Triple
T5099043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chilean Declaration of Independence |
E114936
|
entity |
| Predicate | hasCanonicalDateInChile |
P61089
|
FINISHED |
| Object | February 12, 1818 |
—
|
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: February 12, 1818 | Statement: [Chilean Declaration of Independence, hasCanonicalDateInChile, February 12, 1818]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanonicalDateInChile Context triple: [Chilean Declaration of Independence, hasCanonicalDateInChile, February 12, 1818]
-
A.
isWesternmostChileanTimeZone
Indicates that the referenced time zone is the one located furthest to the west within the territory of Chile.
-
B.
offsetRelativeToChileStandardTime
Indicates that a time value is expressed as an offset relative to Chile Standard Time (its base time zone).
-
C.
dateDetermination
Indicates the process or criteria by which a specific date is identified, calculated, or assigned in relation to an event or condition.
-
D.
hasCanonicalDayBeginning
Indicates that there is a designated, standard starting point of the day defined for a given context or system.
-
E.
usesJulianCalendar
Indicates that the subject follows or is based on the Julian calendar system for dating events or timekeeping.
- 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_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. |
| PDg | Predicate description generation | batch_69bd738ac2e0819099c06cdcc5e21d28 |
completed | March 20, 2026, 4:19 p.m. |
Created at: March 20, 2026, 1:40 p.m.