Triple
T31951256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lafkenche people |
E815783
|
entity |
| Predicate | legalInstrumentCountry |
P197879
|
FINISHED |
| Object | Chile |
—
|
NE NERFINISHED |
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: Chile | Statement: [Lafkenche people, legalInstrumentCountry, Chile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalInstrumentCountry Context triple: [Lafkenche people, legalInstrumentCountry, Chile]
-
A.
countryJurisdiction
Indicates that one country has legal authority, control, or governing power over a specified territory, entity, or matter.
-
B.
countryLegalFramework
Indicates the legal system, regulations, and institutional rules that govern actions and relationships within a given country.
-
C.
countryOfJurisdiction
Indicates the country whose legal authority or jurisdiction governs or applies to a given entity, action, or arrangement.
-
D.
legalLicenseJurisdiction
Indicates the legal authority or geographic area under whose laws a particular license is granted, valid, or enforced.
-
E.
legalSystemRegion
Indicates the geographic or jurisdictional region within which a particular legal system is applicable or in force.
- F. None of above. chosen
Provenance (4 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69feb5e66224819083b87c3707a5a5e0 |
completed | May 9, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69feb3bd700c8190991ed200cd3c04db |
completed | May 9, 2026, 4:10 a.m. |
| PDg | Predicate description generation | batch_69feb5e50a7481908d6bff55bd85e06d |
completed | May 9, 2026, 4:19 a.m. |
Created at: May 1, 2026, 12:07 a.m.