Triple
T29821120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Tarapacá |
E757246
|
entity |
| Predicate | forceChile |
P168186
|
FINISHED |
| Object | approximately 2,800 troops |
—
|
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: approximately 2,800 troops | Statement: [Battle of Tarapacá, forceChile, approximately 2,800 troops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forceChile Context triple: [Battle of Tarapacá, forceChile, approximately 2,800 troops]
-
A.
statusInChile
Indicates the legal, social, or operational status that an entity holds specifically within the context of Chile.
-
B.
areaInChile
Indicates that a place, region, or geographic area is located within the national territory of Chile.
-
C.
commanderForChile
Indicates that an individual serves or has served as a military or organizational commander on behalf of Chile.
-
D.
rankByAreaInChile
Indicates the relative ordering of entities based on their area size within the geographic boundaries of Chile.
-
E.
isPartOfChileanTerritory
Indicates that one entity is geographically or politically included within the official territory of Chile.
- 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_69f2245701c88190ad42415a0956c4ed |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f675675250819089db3b30f1f05f87 |
completed | May 2, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 5:29 p.m.