Triple
T33906825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kwere people |
E869203
|
entity |
| Predicate | modernStateContext |
P87219
|
FINISHED |
| Object | United Republic of Tanzania |
—
|
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: United Republic of Tanzania | Statement: [Kwere people, modernStateContext, United Republic of Tanzania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernStateContext Context triple: [Kwere people, modernStateContext, United Republic of Tanzania]
-
A.
modernState
Indicates that an entity functions as a contemporary, currently existing state or nation in the modern era.
-
B.
modernStateSuccessor
Indicates that one modern state is the legal, political, or historical successor to another earlier state.
-
C.
modernStateName
chosen
Indicates that an entity is identified by the name of the corresponding modern (current) state or country.
-
D.
contemporaryState
Indicates that two entities exist or occur during the same time period or historical era.
-
E.
modernClaimantState
Indicates that a state is the contemporary political entity that claims continuity with, or succession from, an earlier historical state.
- 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_69f34997703c8190866b1d404bce531f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: May 1, 2026, 1:48 a.m.