Triple
T28091059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaugirard (Paris Métro) |
E709953
|
entity |
| Predicate | convertedToLine |
P169273
|
FINISHED |
| Object | Paris Métro Line 12 |
—
|
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 12 | Statement: [Vaugirard (Paris Métro), convertedToLine, Paris Métro Line 12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convertedToLine Context triple: [Vaugirard (Paris Métro), convertedToLine, Paris Métro Line 12]
-
A.
definedLine
Indicates that a specific line (such as a boundary, path, or reference line) has been formally established or specified within a given context.
-
B.
formedLine
Indicates that an entity has arranged itself or others into a line or linear formation.
-
C.
throughServiceToLine
Indicates that a service operates through or along a specified line, establishing a through-service relationship between the service and the line.
-
D.
builtLine
Indicates that an entity constructed or established a particular line, such as a route, boundary, or infrastructure segment.
-
E.
originalLine
Indicates that one entity is the initial or source version of a line from which other versions or derivatives may originate.
- F. None of above. chosen
Provenance (4 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_69ef9b70fd108190a875953b2e50ca91 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f67d691a948190afa7fb19ae7d4ac5 |
completed | May 2, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67c9ec1708190b26ccf402ed7b106 |
completed | May 2, 2026, 10:37 p.m. |
Created at: April 27, 2026, 8:58 p.m.