Triple
T29717171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heilsberg |
E751943
|
entity |
| Predicate | battleOccurredInWar |
P62977
|
FINISHED |
| Object | War of the Fourth Coalition |
—
|
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: War of the Fourth Coalition | Statement: [Heilsberg, battleOccurredInWar, War of the Fourth Coalition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleOccurredInWar Context triple: [Heilsberg, battleOccurredInWar, War of the Fourth Coalition]
-
A.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
-
B.
battleOccurredNear
Indicates that a battle took place in spatial proximity to a specified location or entity.
-
C.
battleOccurredOn
Indicates that a specific battle took place at or on a particular location or date.
-
D.
battleWasPartOf
chosen
Indicates that a specific battle occurred as a component or phase within a larger military campaign, war, or conflict.
-
E.
battleInvolvedIn
Indicates that an entity participated as a combatant or directly took part in a specific battle or military engagement.
- 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672dd9ab881908969657a9bd48098 |
completed | May 2, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:34 p.m.