Triple
T24767208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amravati division |
E619617
|
entity |
| Predicate | hasDivisionalHeadquarters |
P55416
|
FINISHED |
| Object | Amravati |
—
|
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: Amravati | Statement: [Amravati division, hasDivisionalHeadquarters, Amravati]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDivisionalHeadquarters Context triple: [Amravati division, hasDivisionalHeadquarters, Amravati]
-
A.
isDivisionalHeadquartersOf
chosen
Indicates that one entity serves as the main administrative or management headquarters for a specific division of another entity.
-
B.
hasHigherHeadquarters
Indicates that one organizational unit serves as the superior or parent headquarters overseeing another unit.
-
C.
partOfHeadquarters
Indicates that one entity is a component, subdivision, or unit within the headquarters of another entity.
-
D.
hasHindquartersOf
Indicates that one entity possesses or exhibits the hindquarters characteristic or form of another entity.
-
E.
subdivisionHeadquartersOf
Indicates that a location serves as the main administrative headquarters for a specific subdivision of a larger organization 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_69e2fabd04488190a2d13c97be745a2d |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 18, 2026, 4:28 a.m.