Triple
T32349371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Fort Erie (1866) |
E826550
|
entity |
| Predicate | combatantOrigin |
P166913
|
FINISHED |
| Object | United States (Fenian raiders) |
—
|
NE NERFINISHED |
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: United States (Fenian raiders) | Statement: [Battle of Fort Erie (1866), combatantOrigin, United States (Fenian raiders)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatantOrigin Context triple: [Battle of Fort Erie (1866), combatantOrigin, United States (Fenian raiders)]
-
A.
combatantsOrigin
chosen
Indicates the place or source from which the participants in a conflict or fight originate.
-
B.
combatantsNationality
Indicates that the entities involved in a combat or conflict share or are associated with a specified nationality.
-
C.
countryForWhichFought
Indicates the country on whose behalf or under whose authority an entity participated in a conflict or war.
-
D.
militaryOrigin
Indicates that an entity originates from, was created by, or is derived from a military organization, context, or background.
-
E.
combatantTribe
Indicates a tribal group that participates as a fighter or belligerent party in a conflict or battle.
- 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_69f34914dfc48190a390cd0720d9e86f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 12:49 a.m.