Triple
T36270045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jebero |
E892643
|
entity |
| Predicate | hasStatusInPeru |
P24028
|
FINISHED |
| Object | indigenous language of Peru |
—
|
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: indigenous language of Peru | Statement: [Jebero, hasStatusInPeru, indigenous language of Peru]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStatusInPeru Context triple: [Jebero, hasStatusInPeru, indigenous language of Peru]
-
A.
statusInPeru
chosen
Indicates the legal, social, or operational condition or standing that something or someone has within the context of Peru.
-
B.
statusInChile
Indicates the legal, social, or operational status that an entity holds specifically within the context of Chile.
-
C.
statusInBolivia
Indicates the legal, social, or operational condition or standing that something or someone has within the context of Bolivia.
-
D.
statusInArgentina
Indicates the legal, social, or official standing or condition that something or someone has within the context of Argentina.
-
E.
statusInEcuador
Indicates the legal, social, or official condition or standing that an entity has within the context of Ecuador.
- 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_69f76e488f34819083e254dbe288c27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a003f6083608190a5deadc7291cf70e |
completed | May 10, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_6a003c935c40819085fdb255a52ba03b |
completed | May 10, 2026, 8:06 a.m. |
Created at: May 3, 2026, 4:09 p.m.