Triple
T5096157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pratzen Heights |
E114868
|
entity |
| Predicate | battleOutcomeAssociated |
P19109
|
FINISHED |
| Object | decisive French victory |
—
|
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: decisive French victory | Statement: [Pratzen Heights, battleOutcomeAssociated, decisive French victory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleOutcomeAssociated Context triple: [Pratzen Heights, battleOutcomeAssociated, decisive French victory]
-
A.
resultOfBattle
chosen
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
-
B.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
-
C.
battleOutcomeRole
Indicates the specific role an entity played in a battle with respect to its outcome (e.g., victor, loser, ally, defender).
-
D.
associatedWithBattle
Indicates a relationship where an entity is connected or linked to a specific battle, such as by participation, relevance, or involvement.
-
E.
battleDateRelation
Indicates the temporal relationship specifying on which date a particular battle or combat event took place.
- 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_69bd443fc49c819089629c00e311310c |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75652a8081908386718f1fdb1de3 |
completed | March 20, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69bd715e06808190931934dc9930f997 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:40 p.m.