Triple
T20733316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crossroads of Freedom: Antietam |
E509625
|
entity |
| Predicate | placesEventWithin |
P19113
|
FINISHED |
| Object | broader context of world history |
—
|
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: broader context of world history | Statement: [Crossroads of Freedom: Antietam, placesEventWithin, broader context of world history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placesEventWithin Context triple: [Crossroads of Freedom: Antietam, placesEventWithin, broader context of world history]
-
A.
takesPlace
Indicates that an event or action occurs or is situated at a particular time, place, or context.
-
B.
eventIn
chosen
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
-
C.
eventUse
Indicates that an event involves the use or utilization of a particular entity (e.g., a resource, tool, or method) as part of its occurrence.
-
D.
organisedEvent
Indicates that an entity planned, coordinated, and carried out an event.
-
E.
placeNamedAfterEvent
Indicates that a place derives its name from a specific historical event or occurrence.
- 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.