Triple
T23409243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hla’alua |
E560018
|
entity |
| Predicate | recognizedAsIndigenousGroupInYear |
P56771
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Hla’alua, recognizedAsIndigenousGroupInYear, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedAsIndigenousGroupInYear Context triple: [Hla’alua, recognizedAsIndigenousGroupInYear, 2014]
-
A.
recognizedAsIndigenousPeopleBy
Indicates that one party formally acknowledges and accepts another party as belonging to an indigenous people or community.
-
B.
recognizedAsIndigenousIn
Indicates that an entity is officially acknowledged or classified as Indigenous within a specified region, country, or jurisdiction.
-
C.
recognizedAsTribeInYear
chosen
Indicates that an entity was officially recognized or designated as a tribe in a specified year.
-
D.
representsIndigenousGroup
Indicates that one entity is an indigenous group associated with, or represented by, another entity.
-
E.
broaderIndigenousGrouping
Indicates that one indigenous group is a broader, more inclusive grouping that encompasses another, more specific indigenous group.
- 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_69e2454b3a5881909c64773dc8a5d289 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a50fff10819094e71fb0c11b7d95 |
completed | April 29, 2026, 6:28 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:38 p.m.