Triple
T31178667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arni |
E794827
|
entity |
| Predicate | locatedInDistrictWithHeadquarters |
P181016
|
FINISHED |
| Object | Yavatmal |
—
|
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: Yavatmal | Statement: [Arni, locatedInDistrictWithHeadquarters, Yavatmal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInDistrictWithHeadquarters Context triple: [Arni, locatedInDistrictWithHeadquarters, Yavatmal]
-
A.
headquartersDistrict
Indicates the administrative district or area where an organization’s main headquarters is located.
-
B.
basedInDistrict
Indicates that an entity is located or has its primary base of operations within a specific administrative district.
-
C.
partOfHeadquarters
Indicates that one entity is a component, subdivision, or unit within the headquarters of another entity.
-
D.
headquartersLocation
Indicates the place where an organization’s main administrative center or principal office is located.
-
E.
districtHeadquarterWithin
chosen
Indicates that the administrative headquarters of a district is located within the boundaries of a specified area or entity.
- 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_69f224d675d08190957198068e440422 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a0160834e388190908591b300954d29 |
completed | May 11, 2026, 4:52 a.m. |
| PD | Predicate disambiguation | batch_6a01602a83408190a11d754bdc7da0e9 |
completed | May 11, 2026, 4:50 a.m. |
Created at: April 29, 2026, 9:08 p.m.