Triple
T24832082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waiwai |
E621365
|
entity |
| Predicate | politicalStatusInBrazil |
P155001
|
FINISHED |
| Object | recognized Indigenous group |
—
|
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: recognized Indigenous group | Statement: [Waiwai, politicalStatusInBrazil, recognized Indigenous group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalStatusInBrazil Context triple: [Waiwai, politicalStatusInBrazil, recognized Indigenous group]
-
A.
statusInBrazil
chosen
Indicates the legal, social, or operational status that an entity holds specifically within the context of Brazil.
-
B.
politicalStatusContext
Indicates the situational or contextual conditions under which a particular political status holds or is evaluated.
-
C.
legalStatusInPortugal
Indicates the legal status or classification that an entity holds specifically within the jurisdiction of Portugal.
-
D.
BrazilNeededResult
Indicates that Brazil required or depended on a particular outcome or result to occur or be achieved.
-
E.
significantPopulationInBrazilianState
Indicates that a population group or entity has a notably large or important presence within a specific Brazilian state.
- 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_69e2fac0c3b881909110e5a56c6fa46f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 5:16 a.m.