Triple
T18012390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Congress of Apatzingán |
E430914
|
entity |
| Predicate | startDatePrecision |
P97853
|
FINISHED |
| Object | day |
—
|
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: day | Statement: [Congress of Apatzingán, startDatePrecision, day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startDatePrecision Context triple: [Congress of Apatzingán, startDatePrecision, day]
-
A.
startDate
Indicates the point in time when an event, state, or relationship begins.
-
B.
morePreciseDate
chosen
Indicates that one date value specifies a more detailed or exact point in time than another related date value.
-
C.
startDateConstraint
Indicates a restriction or condition placed on when something is allowed to start, typically specifying valid or required start dates.
-
D.
startDateRule
Indicates the rule or condition that determines when something is allowed or required to start.
-
E.
startDateNewStyle
Indicates the date on which something begins, expressed according to the New Style (Gregorian) calendar rather than the Old Style (Julian) calendar.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b520ea088190b74903f1e1ba49e2 |
completed | April 19, 2026, 10:57 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:24 a.m.