Triple
T28930109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inca–Mapuche conflicts |
E733756
|
entity |
| Predicate | regionDemarcated |
P193597
|
FINISHED |
| Object | southern frontier of the Inca Empire in Chile |
—
|
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: southern frontier of the Inca Empire in Chile | Statement: [Inca–Mapuche conflicts, regionDemarcated, southern frontier of the Inca Empire in Chile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionDemarcated Context triple: [Inca–Mapuche conflicts, regionDemarcated, southern frontier of the Inca Empire in Chile]
-
A.
regionShaped
Indicates that one region determines or influences the shape or form of another region.
-
B.
regionException
Indicates an exception or exclusion to a rule, condition, or classification that applies specifically to a certain region or set of regions.
-
C.
districtRegion
Indicates that a district is located within or belongs administratively to a specific region.
-
D.
regionRuled
Indicates that a particular region is governed or controlled by a specified ruler or authority.
-
E.
regionSub
Indicates that one region is a subregion or contained part of another, larger region.
- 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_69f05b0b49b08190b8994b339c7980f6 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
| PDg | Predicate description generation | batch_69fd4d16dd20819096957c40f43cd971 |
completed | May 8, 2026, 2:40 a.m. |
Created at: April 28, 2026, 8:27 a.m.