Triple
T24091519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xetá |
E596795
|
entity |
| Predicate | hasVulnerabilityStatus |
P67454
|
FINISHED |
| Object | threatened indigenous people |
—
|
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: threatened indigenous people | Statement: [Xetá, hasVulnerabilityStatus, threatened indigenous people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVulnerabilityStatus Context triple: [Xetá, hasVulnerabilityStatus, threatened indigenous people]
-
A.
hasRemediationStatus
Indicates the current state or progress of remediation efforts applied to an identified issue, risk, or non-compliance.
-
B.
associatedWithVulnerability
chosen
Indicates a relationship where an entity is linked to, affected by, or relevant to a specific vulnerability or security weakness.
-
C.
hasVersionStatus
Indicates that an entity is associated with a particular version state or status within its lifecycle or revision history.
-
D.
hasRiskStatus
Indicates the level or category of risk currently associated with an entity.
-
E.
hasVaultStatus
Indicates that an entity possesses a particular vault-related state or condition, such as being stored in, protected by, or associated with a vault.
- 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_69e288c4638c81909bacc28a1e3d436b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dc2e672c8190b3e4be041835cc27 |
completed | April 29, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 10:53 p.m.