Triple
T12242212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Churubusco |
E291760
|
entity |
| Predicate | dateText |
P6878
|
FINISHED |
| Object | 20 August 1847 |
—
|
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: 20 August 1847 | Statement: [Battle of Churubusco, dateText, 20 August 1847]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateText Context triple: [Battle of Churubusco, dateText, 20 August 1847]
-
A.
date
Indicates that two entities are engaged in or participate in a romantic or social outing or relationship with each other.
-
B.
dateOf
chosen
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
C.
dateNotation
Indicates how a date is written or formatted in notation (e.g., order and style of day, month, and year).
-
D.
dateDescription
Indicates a textual description or label that characterizes the nature, context, or details of a particular date or dating event between entities.
-
E.
dateWordAdded
Indicates the specific date on which a particular word was added to a collection, system, or dataset.
- 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d924a3973c8190a882046963b320fb |
completed | April 10, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69d91c41bcbc81909782f4e3c571b218 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.