Triple
T1231501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grozny |
E26451
|
entity |
| Predicate | headOfCity |
P16141
|
FINISHED |
| Object | mayor of Grozny |
—
|
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: mayor of Grozny | Statement: [Grozny, headOfCity, mayor of Grozny]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headOfCity Context triple: [Grozny, headOfCity, mayor of Grozny]
-
A.
headOfOffice
Indicates that one entity serves as the chief or leading authority in charge of a particular office or organizational unit.
-
B.
headOfGovernmentBody
Indicates that one entity serves as the chief executive or leading official in charge of governing another entity, typically a political or administrative body.
-
C.
hasCityManager
chosen
Indicates that an entity has a specific individual who serves in the role of city manager for it.
-
D.
governingHead
Indicates that one entity serves as the ruling or administrative authority over another entity, acting as its primary leader or head.
-
E.
isHeadOf
Indicates that one entity holds the leading or principal authority position over another entity, such as an organization, group, or department.
- 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_69a4948571c88190a9191e451e6035fd |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be5a25348190a0665b6324c4d8f5 |
completed | March 1, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69a4bb65d61c8190bf0424ea0019a98b |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.