Triple
T8436340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Maule |
E199232
|
entity |
| Predicate | southernBoundaryFor |
P13333
|
FINISHED |
| Object | Inca influence 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: Inca influence in Chile | Statement: [Battle of the Maule, southernBoundaryFor, Inca influence in Chile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: southernBoundaryFor Context triple: [Battle of the Maule, southernBoundaryFor, Inca influence in Chile]
-
A.
southernBoundaryReference
chosen
Indicates that one entity is used as the reference or defining limit for the southern boundary of another entity.
-
B.
northernBoundaryReference
Indicates the feature or element that serves as the reference for defining the northern boundary of something.
-
C.
northernBoundaryExtendedTo
Indicates that the northern boundary of one entity has been lengthened or expanded to reach or include another specified reference point or area.
-
D.
isOnSouthernPartOf
Indicates that one entity is located on the southern part or southern region of another entity.
-
E.
isSouthernmostPartOf
Indicates that one entity is the geographically furthest south portion or section of another entity.
- 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_69ca8314cd6c8190a6b8c2a1096e18f3 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe30fba4081908bfdef3faf5baceb |
completed | March 31, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69cbd0ec200c8190b0299e2b0b4bdcc2 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:08 p.m.