Triple
T30551470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nord-Sud line A |
E777570
|
entity |
| Predicate | terminusAfterCompletion |
P388
|
FINISHED |
| Object | Porte de la Chapelle |
—
|
NE NERFINISHED |
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: Porte de la Chapelle | Statement: [Nord-Sud line A, terminusAfterCompletion, Porte de la Chapelle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusAfterCompletion Context triple: [Nord-Sud line A, terminusAfterCompletion, Porte de la Chapelle]
-
A.
terminatesOn
Indicates that one process, event, or state causes or marks the ending of another at a specific time or condition.
-
B.
successorTerminus
Indicates that one terminus directly follows another in a defined sequence or progression.
-
C.
terminus
chosen
Indicates that one entity serves as the final endpoint or stopping place for another entity’s movement, route, or process.
-
D.
terminatesFor
Indicates that one entity causes or marks the ending or cessation of another entity, process, or state.
-
E.
terminateIn
Indicates that one entity ends, concludes, or comes to a stop within, at, or because of another entity or condition.
- 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_69f2249e19108190a458ab446096bf22 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 29, 2026, 8:20 p.m.