Triple
T3259518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strasbourg tramway |
E68375
|
entity |
| Predicate | previousSystemClosed |
P46926
|
FINISHED |
| Object | 1960 |
—
|
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: 1960 | Statement: [Strasbourg tramway, previousSystemClosed, 1960]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousSystemClosed Context triple: [Strasbourg tramway, previousSystemClosed, 1960]
-
A.
closedDuring
Indicates that an entity is not open or available for use during a specified time period or under certain conditions.
-
B.
closedBy
Indicates that one entity performs the action of closing, finishing, or terminating another entity (such as a task, issue, or process).
-
C.
closedAsTerminal
Indicates that a process, case, or interaction has been concluded in a final, non-reopenable (terminal) state.
-
D.
previousFileSystem
Indicates that one file system existed or was in use before another file system in a temporal or versioning sequence.
-
E.
closedUnder
Indicates that applying a specified operation to elements within a set always produces a result that is also an element of that same set.
- F. None of above. chosen
Provenance (4 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_69ad858f74408190bcbd07f967cd7bd0 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adafa4f40c81909adfd0f7f568e3ce |
completed | March 8, 2026, 5:19 p.m. |
| PD | Predicate disambiguation | batch_69ada41ae74081909a0d1d696be8e35e |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada525bb2c8190b773efe6d696b6ab |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:09 p.m.