Triple
T17369708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Pasqual Band of Diegueño Mission Indians |
E422277
|
entity |
| Predicate | hasTribalStatus |
P58167
|
FINISHED |
| Object | federally recognized |
—
|
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: federally recognized | Statement: [San Pasqual Band of Diegueño Mission Indians, hasTribalStatus, federally recognized]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTribalStatus Context triple: [San Pasqual Band of Diegueño Mission Indians, hasTribalStatus, federally recognized]
-
A.
hasTribalAuthority
Indicates that an entity holds recognized governing or decision-making power within a specific tribe or tribal community.
-
B.
hasTribalEnrollment
Indicates that an entity is formally enrolled as a member of a specific tribe or tribal nation.
-
C.
tribalStatus
chosen
Indicates that an entity holds a particular affiliation, recognition, or classification with respect to a tribe or tribal community.
-
D.
hasTribalRegister
Indicates that an entity is officially recorded or listed in a recognized tribal registry or roll.
-
E.
hasTribalPresence
Indicates that a tribal group is present, active, or represented in relation to the referenced entity or location.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a6842388190940235198fa50041 |
completed | April 19, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.