Triple
T8378123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egnatia Odos |
E197624
|
entity |
| Predicate | substantiallyCompleted |
P1574
|
FINISHED |
| Object | late 2000s |
—
|
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: late 2000s | Statement: [Egnatia Odos, substantiallyCompleted, late 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: substantiallyCompleted Context triple: [Egnatia Odos, substantiallyCompleted, late 2000s]
-
A.
completedIn
chosen
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
B.
completedBy
Indicates that a task, process, or action has been finished or carried out by a particular entity.
-
C.
isComplete
Indicates that an action, process, or object has finished all required steps or reached its final state with nothing remaining to be done.
-
D.
partiallyCompleted
Indicates that an action, process, or task has been started and progressed to some extent, but has not yet been fully completed.
-
E.
alsoCompletedBy
Indicates that the same task, activity, or item has been completed by an additional agent or entity besides the one already referenced.
- 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_69ca82f64c188190af4e1608036b865d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80c229708190b813f5e7e44e10d4 |
completed | March 31, 2026, 8:07 a.m. |
| PD | Predicate disambiguation | batch_69cb70cfe82881909fe374ba52649e84 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:02 p.m.