Triple
T26211081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dijon–Vallorbe line |
E655488
|
entity |
| Predicate | endPointCityCountry |
P151489
|
FINISHED |
| Object | Dijon, France |
—
|
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: Dijon, France | Statement: [Dijon–Vallorbe line, endPointCityCountry, Dijon, France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endPointCityCountry Context triple: [Dijon–Vallorbe line, endPointCityCountry, Dijon, France]
-
A.
endPointIsCapitalOf
Indicates that the endpoint entity serves as the capital city of the other related entity (typically a country, state, or region).
-
B.
countryEndpoint
Indicates a connection or interface that serves as the access point or boundary for interactions involving a specific country.
-
C.
connectsCapitalOf
Indicates a relationship where one entity serves as the capital city of another entity, linking the capital to the political or administrative unit it represents.
-
D.
centralCityCountry
chosen
Indicates that a given city is the primary or central city associated with a specified country.
-
E.
countryEnd
Indicates that a country ceases to exist or loses its status as an independent political entity at a specified time or event.
- 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60d1706d481908ca3c7c39ba0d157 |
completed | May 2, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69f5b007ec1c819092e2c3605933f60b |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:52 p.m.