Triple
T15550852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tramway T13 Express |
E370737
|
entity |
| Predicate | futureExtension |
P54844
|
FINISHED |
| Object | extension towards Achères |
—
|
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: extension towards Achères | Statement: [Tramway T13 Express, futureExtension, extension towards Achères]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: futureExtension Context triple: [Tramway T13 Express, futureExtension, extension towards Achères]
-
A.
plannedExtensionTo
chosen
Indicates that one entity is intended or scheduled to be extended, expanded, or continued by another entity in the future.
-
B.
futureComponentOf
Indicates that one entity is expected or planned to become a component or part of another entity at some point in the future.
-
C.
laterFeature
Indicates that one feature, event, or element occurs or is introduced after another in time.
-
D.
formerExtension
Indicates that one entity previously served as an extension or subsidiary part of another entity, but no longer holds that status.
-
E.
futureServes
Indicates that, at a future time, one entity will perform a service or act in a serving role for 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_69d85cc6cf40819091f4a5facee1ebe6 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04a9551288190a583e8291c35f521 |
completed | April 16, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:08 a.m.