Triple
T20733309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crossroads of Freedom: Antietam |
E509625
|
entity |
| Predicate | eventDateCovered |
P10199
|
FINISHED |
| Object | September 17, 1862 |
—
|
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: September 17, 1862 | Statement: [Crossroads of Freedom: Antietam, eventDateCovered, September 17, 1862]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventDateCovered Context triple: [Crossroads of Freedom: Antietam, eventDateCovered, September 17, 1862]
-
A.
eventDateContext
Indicates the contextual role or significance that a specific date has within an event (e.g., whether it is the start, end, deadline, or another relevant temporal marker).
-
B.
eventDateAtLocation
Indicates that a specific event occurs on a particular date at a given location.
-
C.
notableEventCoverage
chosen
Indicates that there is media or documented coverage specifically focused on a notable event related to the subject.
-
D.
eventOccurredAt
Indicates that a particular event took place at a specific time or location.
-
E.
mainEventDate
Indicates the primary or most significant date on which the referenced event occurs or is scheduled to occur.
- 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_69e0b4c589c08190834fb5d86d0efa2b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1ef3040819085c8056e75571104 |
completed | April 21, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69e5c04b31248190b9b9d91b5cb854e3 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:31 p.m.