Triple
T6130435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M66 motorway |
E136702
|
entity |
| Predicate | fullyCompletedBy |
P1574
|
FINISHED |
| Object | 1990s |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 1990s | Statement: [M66 motorway, fullyCompletedBy, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullyCompletedBy Context triple: [M66 motorway, fullyCompletedBy, 1990s]
-
A.
alsoCompletedBy
Indicates that the same task, activity, or item has been completed by an additional agent or entity besides the one already referenced.
-
B.
completedBy
Indicates that a task, process, or action has been finished or carried out by a particular entity.
-
C.
completedIn
chosen
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
D.
completedBefore
Indicates that one event or action was fully completed prior to the start or completion of another specified event or action.
-
E.
isCompleteOn
Indicates that an activity, task, or process has been fully finished or achieved by a specific point in time or on a specific date.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69c008a0a37c81908e5b4f879158afb3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05c4de9c48190b98f67a6251ec1df |
completed | March 22, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c055f19b0c81908be34a00ab218723 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:15 p.m.