Triple
T34581107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow Central Diameters |
E887902
|
entity |
| Predicate | planningModelledOn |
P33328
|
FINISHED |
| Object | Paris RER |
—
|
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 RER | Statement: [Moscow Central Diameters, planningModelledOn, Paris RER]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planningModelledOn Context triple: [Moscow Central Diameters, planningModelledOn, Paris RER]
-
A.
planningModelFor
chosen
Indicates that one entity serves as a planning model used to guide, simulate, or structure the planning activities related to another entity.
-
B.
plannedVia
Indicates that something is arranged, organized, or scheduled by means of a particular method, process, or intermediary.
-
C.
plannedMode
Indicates that a particular mode, method, or state has been intentionally selected or scheduled in advance for use.
-
D.
planningSystem
Indicates that an entity functions as or is associated with a system responsible for organizing, scheduling, or coordinating plans or activities.
-
E.
plannedWith
Indicates that an entity created or arranged a plan in collaboration or coordination with another 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_69f349d25cbc8190869998de5915886b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 1, 2026, 2:03 a.m.