Triple
T7790209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blood River |
E187356
|
entity |
| Predicate | battleDateAtSite |
P19740
|
FINISHED |
| Object | 16 December 1838 |
—
|
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: 16 December 1838 | Statement: [Blood River, battleDateAtSite, 16 December 1838]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleDateAtSite Context triple: [Blood River, battleDateAtSite, 16 December 1838]
-
A.
battleOccurredOn
Indicates that a specific battle took place at or on a particular location or date.
-
B.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
-
C.
battleOccurredNear
Indicates that a battle took place in spatial proximity to a specified location or entity.
-
D.
battleDateRelation
chosen
Indicates the temporal relationship specifying on which date a particular battle or combat event took place.
-
E.
battleWasPartOf
Indicates that a specific battle occurred as a component or phase within a larger military campaign, war, or conflict.
- 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_69ca82af2d2c8190963861f5e0b8bf21 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cae7ea13f08190a60c5f1863bce816 |
completed | March 30, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69caa488532c819093ac40bba0b3c7ef |
completed | March 30, 2026, 4:27 p.m. |
Created at: March 30, 2026, 4:25 p.m.