Triple
T432437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northwest Indian War |
E9741
|
entity |
| Predicate | dateOfBattle |
P10394
|
FINISHED |
| Object | Battle of Fallen Timbers, 1794 |
—
|
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: Battle of Fallen Timbers, 1794 | Statement: [Northwest Indian War, dateOfBattle, Battle of Fallen Timbers, 1794]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfBattle Context triple: [Northwest Indian War, dateOfBattle, Battle of Fallen Timbers, 1794]
-
A.
battleOccurredOn
Indicates that a specific battle took place at or on a particular location or date.
-
B.
yearOfBattle
chosen
Indicates the specific calendar year in which a particular battle took place.
-
C.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
-
D.
battleDateRange
Indicates the time span during which a particular battle or military engagement took place.
-
E.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
- 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_69a2e801e1d48190b505d1dd336b52ac |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eef07e748190b05392778f3de980 |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd9264c8190b92f9a50348e5541 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.