Triple
T4746452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federated Indians of Graton Rancheria |
E105369
|
entity |
| Predicate | stateRecognized |
P4088
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Federated Indians of Graton Rancheria, stateRecognized, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateRecognized Context triple: [Federated Indians of Graton Rancheria, stateRecognized, yes]
-
A.
recognizedNewState
Indicates that an entity has formally acknowledged or accepted the existence or authority of a newly established state or political entity.
-
B.
resultRecognizedBy
Indicates that a particular result is formally acknowledged, validated, or accepted by a specified recognizing entity.
-
C.
recognitionStatus
Indicates the current state or outcome of acknowledging, validating, or officially accepting something or someone.
-
D.
coreValueRecognized
Indicates that a fundamental principle or core value associated with an entity has been acknowledged or identified by another entity or system.
-
E.
stateRecognizedTribe
chosen
Indicates that a tribe is officially acknowledged and recognized by a state government as a tribal entity.
- 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_69bd43ef87a48190a5bc3600711aa032 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64c3fcb081909b1fe867b4adac8b |
completed | March 20, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69bd6223defc8190823665a6592c1154 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.