Triple
T2694854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Satara |
E58486
|
entity |
| Predicate | stateCapitalDistanceApprox |
P10889
|
FINISHED |
| Object | about 110 km from Pune |
—
|
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: about 110 km from Pune | Statement: [Satara, stateCapitalDistanceApprox, about 110 km from Pune]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateCapitalDistanceApprox Context triple: [Satara, stateCapitalDistanceApprox, about 110 km from Pune]
-
A.
stateCapitalProximity
Indicates the spatial closeness or distance between a state’s capital city and another specified location.
-
B.
distanceFromCapital
chosen
Indicates the measured distance between a given location and the capital city of its corresponding region or country.
-
C.
governingStateCapital
Indicates that a state serves as the governing political authority over the specified capital city.
-
D.
regionCapital
Indicates that one entity is the capital city or administrative center of a specified region.
-
E.
stateCapitalFunction
Indicates that one location serves as the official capital city and primary seat of government for a given state.
- 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_69ab4ac269e481909cb317d79e68b75b |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda10a9bc81908473d02ab9116cef |
completed | March 7, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69abd81ea5d88190ab5c8f8b8064b931 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.