Triple
T5370096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nantes tramway |
E108825
|
entity |
| Predicate | firstGenerationClosureDate |
P25153
|
FINISHED |
| Object | 1958 |
—
|
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: 1958 | Statement: [Nantes tramway, firstGenerationClosureDate, 1958]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstGenerationClosureDate Context triple: [Nantes tramway, firstGenerationClosureDate, 1958]
-
A.
firstGenerationStart
Indicates the point in time or event at which the first generation in a sequence, lineage, or series begins.
-
B.
firstGenerationEnd
chosen
Indicates the point in time or event at which the first generation in a sequence, lineage, or process concludes.
-
C.
firstGeneration
Indicates that an entity belongs to the first generation within a defined lineage, sequence, or series relative to other related entities.
-
D.
firstGenerationReleaseDate
Indicates the calendar date on which the first generation or initial version of something was officially released.
-
E.
firstIntroductionDate
Indicates the date on which an entity was first introduced or presented for the first time.
- 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_69bd440c77948190aad2a5f39b7b80f5 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd88801b188190b9ac35ed89167fa3 |
completed | March 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69bd846172788190969f24bc7503c05e |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:02 p.m.