Triple
T35466308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ley Indígena 19.253 |
E1025082
|
entity |
| Predicate | estableceConcepto |
P201
|
FINISHED |
| Object | tierras indígenas |
—
|
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: tierras indígenas | Statement: [Ley Indígena 19.253, estableceConcepto, tierras indígenas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estableceConcepto Context triple: [Ley Indígena 19.253, estableceConcepto, tierras indígenas]
-
A.
addsConcept
Indicates that one entity introduces or incorporates a new concept into another entity, such as a model, document, or knowledge structure.
-
B.
exportsConcept
Indicates that one entity sends or supplies a concept, idea, or abstract knowledge resource from itself to another entity or context.
-
C.
introducedConcept
chosen
Indicates that one entity is responsible for presenting, defining, or bringing a new concept into use or awareness for another entity or context.
-
D.
hasConcept
Indicates that an entity includes, embodies, or is associated with a particular concept.
-
E.
replacesConcept
Indicates that one concept takes the place of, or supersedes, another concept in a given context or system.
- 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_69f76dfa20d0819089585dc2cf653aea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: May 3, 2026, 4:04 p.m.