Triple
T9131119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golden City (Wakanda) |
E219086
|
entity |
| Predicate | governedByCouncil |
P14923
|
FINISHED |
| Object | Wakandan tribal elders |
—
|
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: Wakandan tribal elders | Statement: [Golden City (Wakanda), governedByCouncil, Wakandan tribal elders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governedByCouncil Context triple: [Golden City (Wakanda), governedByCouncil, Wakandan tribal elders]
-
A.
districtCouncil
Indicates that an entity serves as, or is governed by, a district-level council within a larger administrative or political structure.
-
B.
hasCountyCouncil
Indicates that an entity is administratively governed or overseen by a specific county council.
-
C.
council
chosen
Indicates that an entity serves as a governing or advisory council for another entity or within a particular domain.
-
D.
governedCommunity
Indicates that one entity exercises governing authority or administrative control over a community or group of people.
-
E.
hasCityCouncil
Indicates that an entity is governed or administered by a specific city council.
- 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_69ca83debfc0819095800583e97ab10f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8ceea6c81909f368f12dac1649c |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc6601d77881908299d58db6e64937 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:18 p.m.