Triple
T37334663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosebud Creek |
E926855
|
entity |
| Predicate | hasEventDateAtLocation |
P51947
|
FINISHED |
| Object | June 17, 1876 (Battle of the Rosebud) |
—
|
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: June 17, 1876 (Battle of the Rosebud) | Statement: [Rosebud Creek, hasEventDateAtLocation, June 17, 1876 (Battle of the Rosebud)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEventDateAtLocation Context triple: [Rosebud Creek, hasEventDateAtLocation, June 17, 1876 (Battle of the Rosebud)]
-
A.
eventDateAtLocation
chosen
Indicates that a specific event occurs on a particular date at a given location.
-
B.
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).
-
C.
eventOccurredAt
Indicates that a particular event took place at a specific time or location.
-
D.
hasVenueFor
Indicates that one entity provides or serves as the location or setting where an event, activity, or function takes place for another entity.
-
E.
hasDraftEventLocation
Indicates that something is associated with a provisional or draft-specific event location.
- 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_69f76eb4e8a881908bd40da28f36fc7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8c38a9688190be524246f5682107 |
completed | May 6, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9c6e0481908565bd849e869b24 |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.