Triple
T28436726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tehran to Yasuj |
E715286
|
entity |
| Predicate | capitalCityOnRoute |
P121744
|
FINISHED |
| Object | Tehran |
—
|
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: Tehran | Statement: [Tehran to Yasuj, capitalCityOnRoute, Tehran]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalCityOnRoute Context triple: [Tehran to Yasuj, capitalCityOnRoute, Tehran]
-
A.
capitalCityRiding
Indicates that a political riding or electoral district contains or corresponds to the capital city of a given region or jurisdiction.
-
B.
hasMajorCityOnRoute
Indicates that a major city lies along, or is directly served by, a specified route or path between locations.
-
C.
capitalCityInvolved
Indicates that a capital city participates in, is affected by, or plays a role in a specified event, process, or relationship.
-
D.
countryCapitalTraversed
chosen
Indicates that a path, route, or traversal passes through the capital city of a specified country.
-
E.
capitalCityShown
Indicates that the specified capital city is visually displayed or highlighted in a given context (such as a map, interface, or visualization).
- 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_69efd6b253888190b3c7222ed6a403a8 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 28, 2026, 1:43 a.m.