Triple
T1957332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catawba |
E42298
|
entity |
| Predicate | sovereignStatus |
P5545
|
FINISHED |
| Object | tribal government |
—
|
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: tribal government | Statement: [Catawba, sovereignStatus, tribal government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sovereignStatus Context triple: [Catawba, sovereignStatus, tribal government]
-
A.
sovereigntyStatus
chosen
Indicates the degree and type of political independence or control an entity holds over its own territory and governance.
-
B.
sovereignState
Indicates that an entity is recognized as an independent, self-governing state with ultimate authority over its territory and not subject to any higher political power.
-
C.
hasSovereignState
Indicates that one entity is the sovereign state that has ultimate authority or jurisdiction over another entity.
-
D.
denotesSovereignState
Indicates that one entity designates or identifies another entity as a sovereign, independent state.
-
E.
sovereignGovernment
Indicates that a government possesses ultimate authority and independence over a defined territory, free from external control.
- 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_69a8870eea088190a38781990812a9bc |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb68a8e608190bc37a85913b3cd44 |
completed | March 7, 2026, 5:24 a.m. |
| PD | Predicate disambiguation | batch_69abaff5dbd48190a9d36ca60de151db |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.