Triple
T1642981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dyre Avenue Line |
E35514
|
entity |
| Predicate | integrationWithIRTCompleted |
P3055
|
FINISHED |
| Object | 1957 |
—
|
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: 1957 | Statement: [Dyre Avenue Line, integrationWithIRTCompleted, 1957]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: integrationWithIRTCompleted Context triple: [Dyre Avenue Line, integrationWithIRTCompleted, 1957]
-
A.
isComplete
Indicates that an action, process, or object has finished all required steps or reached its final state with nothing remaining to be done.
-
B.
installationCompleted
chosen
Indicates that the process of installing something has finished successfully.
-
C.
inscriptionCompleteness
Indicates how fully or partially an inscription is preserved or recorded in relation to its original state.
-
D.
integrates
Indicates that one entity combines or brings together another entity or set of entities into a unified, functioning whole.
-
E.
integratedIn
Indicates that one entity is incorporated as a component or part within a larger system, structure, or context represented by another entity.
- 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_69a88604618c81908b41f6429c431eb6 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a919306fd48190a245fc95e0e759d9 |
completed | March 5, 2026, 5:48 a.m. |
| PD | Predicate disambiguation | batch_69a907cc9d348190b76b0d3f596e5a81 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.