Triple
T38153080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poarch Creek Indians |
E952807
|
entity |
| Predicate | hasSovereignGovernment |
P19366
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Poarch Creek Indians, hasSovereignGovernment, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSovereignGovernment Context triple: [Poarch Creek Indians, hasSovereignGovernment, true]
-
A.
hasSovereignState
Indicates that one entity is the sovereign state that has ultimate authority or jurisdiction over another entity.
-
B.
sovereignGovernment
chosen
Indicates that a government possesses ultimate authority and independence over a defined territory, free from external control.
-
C.
hasSovereignAuthority
Indicates that one entity holds ultimate governing or ruling power over another entity or domain.
-
D.
hasSovereignPowers
Indicates that an entity possesses ultimate governing authority or supreme political power over a territory or population.
-
E.
hasDeFactoSovereign
Indicates that one entity effectively exercises sovereign authority or control over another entity in practice, regardless of formal or legal recognition.
- 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_69f76f0a67f4819080c492f61d688fcc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: May 3, 2026, 4:21 p.m.