Triple
T17689015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paris–Warsaw |
E440972
|
entity |
| Predicate | capitalToCapitalRoute |
P105217
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Paris–Warsaw, capitalToCapitalRoute, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalToCapitalRoute Context triple: [Paris–Warsaw, capitalToCapitalRoute, true]
-
A.
countryCapitalTraversed
Indicates that a path, route, or traversal passes through the capital city of a specified country.
-
B.
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.
-
C.
capitalFor
Indicates that one entity serves as the capital city or administrative center for another entity, such as a country, state, or region.
-
D.
capitalUnder
Indicates that one entity serves as the capital city or administrative center subordinate to, or governed by, another entity.
-
E.
connectsCapitalsOf
chosen
Indicates a relationship where something serves as a link or route between the capital cities of two regions or countries.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4704a6bb4819083752285baf3b3ee |
completed | April 19, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69e3cde3673c8190a889e14ba1f07dc1 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10:03 a.m.