Triple
T27831863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noisy–Champs station |
E703122
|
entity |
| Predicate | futureLine |
P41765
|
FINISHED |
| Object | Paris Métro Line 15 |
—
|
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 15 | Statement: [Noisy–Champs station, futureLine, Paris Métro Line 15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: futureLine Context triple: [Noisy–Champs station, futureLine, Paris Métro Line 15]
-
A.
futureServes
Indicates that, at a future time, one entity will perform a service or act in a serving role for another entity.
-
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.
futureEvolution
Indicates a predicted or potential future development or transformation of one entity into another.
-
D.
futurePosition
Indicates that one entity will occupy or hold the position, role, or location of another entity at a later point in time.
-
E.
futureSiteOf
chosen
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_69ef840b94b08190950a4f77296938b2 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 5:56 p.m.