Triple
T8819467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sela Pass |
E209863
|
entity |
| Predicate | stateCapitalDirectionFrom |
P84796
|
FINISHED |
| Object | northwest of Itanagar |
—
|
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: northwest of Itanagar | Statement: [Sela Pass, stateCapitalDirectionFrom, northwest of Itanagar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateCapitalDirectionFrom Context triple: [Sela Pass, stateCapitalDirectionFrom, northwest of Itanagar]
-
A.
regionCapital
Indicates that one entity is the capital city or administrative center of a specified region.
-
B.
coCapitalOf
Indicates that two or more cities share the status of being capital cities of the same political or administrative entity.
-
C.
stateCapitalForRegionLocatedAt
Indicates that a city serves as the capital of a particular region and is geographically located at that region.
-
D.
governingStateCapital
Indicates that a state serves as the governing political authority over the specified capital city.
-
E.
stateCapitalRegion
Indicates that a region serves as the capital area or administrative seat for a particular state.
- 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_69ca8364e13081909c85fe80f44fe86f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc600e6e2881908934cbff0ab5d6fd |
completed | April 1, 2026, midnight |
| PD | Predicate disambiguation | batch_69cc5c21e64c81908490e3b0875dc0d6 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cff3608819081d2d7e5c16d44b7 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:46 p.m.