Triple
T5098912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expedition to Chiloé |
E114933
|
entity |
| Predicate | yearOfFinalRoyalistDefeatInChile |
P30917
|
FINISHED |
| Object | 1826 |
—
|
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: 1826 | Statement: [Expedition to Chiloé, yearOfFinalRoyalistDefeatInChile, 1826]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfFinalRoyalistDefeatInChile Context triple: [Expedition to Chiloé, yearOfFinalRoyalistDefeatInChile, 1826]
-
A.
yearOfSurrender
Indicates the specific calendar year in which an entity formally surrendered or yielded, typically ending its resistance or control.
-
B.
endOfTermAsViceroyOfTheRíoDeLaPlata
Indicates the date or point in time when an individual’s tenure as Viceroy of the Río de la Plata concludes.
-
C.
finalDefeatDate
chosen
Indicates the date on which an entity was ultimately and conclusively defeated.
-
D.
battleEndYear
Indicates the calendar year in which a particular battle or military engagement concluded.
-
E.
conquestYear
Indicates the year in which one entity successfully conquered or took control over 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_69bd443fc49c819089629c00e311310c |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7568e9c881909f114973faef6832 |
completed | March 20, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69bd715e06808190931934dc9930f997 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:40 p.m.