Triple
T37434993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porte d'Ivry |
E930239
|
entity |
| Predicate | metroTerminusOf |
P151408
|
FINISHED |
| Object | Paris Métro Line 7 (southeastern branch) |
—
|
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: Paris Métro Line 7 (southeastern branch) | Statement: [Porte d'Ivry, metroTerminusOf, Paris Métro Line 7 (southeastern branch)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metroTerminusOf Context triple: [Porte d'Ivry, metroTerminusOf, Paris Métro Line 7 (southeastern branch)]
-
A.
terminusStation
Indicates that a station serves as the final endpoint or terminal stop for a given route or service.
-
B.
railTerminusFor
chosen
Indicates that one location serves as the final or terminal rail station or endpoint for a specified rail line or service.
-
C.
railLineTerminus
Indicates that a rail line ends or terminates at the specified location or station.
-
D.
railTerminus
Indicates that a railway line or service ends at a particular station or location, which serves as its final terminus.
-
E.
subwayStation
Indicates that one entity is a subway station associated with, located in, or serving the other 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_69f76ebfdcb8819098562ff3db673b04 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.