Triple
T31798748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Rincón |
E811667
|
entity |
| Predicate | yearInChronology |
P68464
|
FINISHED |
| Object | 1825 in South America |
—
|
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: 1825 in South America | Statement: [Battle of Rincón, yearInChronology, 1825 in South America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearInChronology Context triple: [Battle of Rincón, yearInChronology, 1825 in South America]
-
A.
yearCirca
Indicates that the associated year is approximate or uncertain rather than exact.
-
B.
chronologyPreviousYear
Indicates that one time-related entity occurs exactly one calendar year before another in a chronological sequence.
-
C.
yearObserved
Indicates the specific calendar year during which the referenced event, condition, or measurement was observed or recorded.
-
D.
yearInGregorianCalendar
Indicates that a specified year is measured according to the Gregorian calendar system.
-
E.
chronologyOf
chosen
Indicates that one entity represents the temporal ordering, sequence, or historical timeline of events or states associated with 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:41 p.m.