Triple
T36286572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosny–Bois-Perrier |
E893100
|
entity |
| Predicate | futurePartOf |
P42365
|
FINISHED |
| Object | Paris Métro Line 11 |
—
|
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 11 | Statement: [Rosny–Bois-Perrier, futurePartOf, Paris Métro Line 11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: futurePartOf Context triple: [Rosny–Bois-Perrier, futurePartOf, Paris Métro Line 11]
-
A.
futureComponentOf
chosen
Indicates that one entity is expected or planned to become a component or part of another entity at some point in the future.
-
B.
futureServes
Indicates that, at a future time, one entity will perform a service or act in a serving role for another entity.
-
C.
partOfAfter
Indicates that one entity becomes a component or subset of another entity at some point after a specified time or event.
-
D.
formerPart
Indicates that an entity was once a component or member of another entity but is no longer part of it.
-
E.
futureSiteOf
Indicates that a location is planned or designated to become the site of a particular entity or structure in the future.
- 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_69f76e4955c08190b8cfddca34fc0242 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:09 p.m.