Triple
T37435268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Line 6 (Paris Métro) |
E930245
|
entity |
| Predicate | runsOnStructure |
P187814
|
FINISHED |
| Object | viaduct |
—
|
LITERAL FINISHED |
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: viaduct | Statement: [Line 6 (Paris Métro), runsOnStructure, viaduct]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runsOnStructure Context triple: [Line 6 (Paris Métro), runsOnStructure, viaduct]
-
A.
runsUnder
Indicates that one process, task, or component operates within the control, environment, or context provided by another system, platform, or framework.
-
B.
runsVia
Indicates that a process, operation, or connection is executed, routed, or carried out through a specified intermediate channel, path, or mechanism.
-
C.
runsFrom
Indicates that one entity flees or escapes away from another entity.
-
D.
enablesStructure
Indicates that one entity provides the necessary conditions or functionality for another entity to be formed, organized, or structurally realized.
-
E.
rootStructure
Indicates that one entity serves as the primary or foundational structural element upon which another entity is based or organized.
- 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_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. |
| PDg | Predicate description generation | batch_69fb92ee27408190b0116ef2d789abac |
completed | May 6, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:17 p.m.