Triple
T23627229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suhum |
E583499
|
entity |
| Predicate | hasLocalChief |
P150971
|
FINISHED |
| Object | Traditional chief of Suhum |
—
|
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: Traditional chief of Suhum | Statement: [Suhum, hasLocalChief, Traditional chief of Suhum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalChief Context triple: [Suhum, hasLocalChief, Traditional chief of Suhum]
-
A.
hasHeadOfLocalGovernment
Indicates that an administrative area is associated with the person who serves as its chief local government official.
-
B.
hasCurrentChief
chosen
Indicates that one entity currently holds the position of chief or top leader of another entity.
-
C.
hasPoliceChief
Indicates that an entity has, is associated with, or is under the authority of a specific police chief.
-
D.
hasCivicLeader
Indicates that an entity serves as the civic leader (such as a mayor or equivalent public official) of another entity, typically a city or municipality.
-
E.
hasLocalDistrict
Indicates that an entity is associated with or falls under the jurisdiction of a specific local administrative district.
- 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_69e248fc8d74819091bd5baef2f36f6f |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b1e4df248190ac38e4e025bd1140 |
completed | April 29, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:46 p.m.