Triple
T10174526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Zorndorf |
E235815
|
entity |
| Predicate | outcomeSummary |
P92530
|
FINISHED |
| Object | Prussians held the field but failed to destroy the Russian army |
—
|
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: Prussians held the field but failed to destroy the Russian army | Statement: [Battle of Zorndorf, outcomeSummary, Prussians held the field but failed to destroy the Russian army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outcomeSummary Context triple: [Battle of Zorndorf, outcomeSummary, Prussians held the field but failed to destroy the Russian army]
-
A.
outcomeType
Indicates the specific category or nature of the result produced by an event, process, or action.
-
B.
outcomeDocument
Indicates that a particular document serves as the result, product, or formal output generated from a process, event, or action.
-
C.
outcomeOf
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
D.
outcomeFocus
Indicates that the primary emphasis or attention is placed on the results or consequences of an action or process.
-
E.
reasoningSummary
Indicates that an entity provides a condensed explanation or overview of the reasoning or logical steps behind a conclusion, decision, or result.
- F. None of above. chosen
Provenance (4 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_69ca84d1d5f88190ab878a1021ecff68 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdeca0dc508190916f2a1bbb288192 |
completed | April 2, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69cd7c79f21c8190a7f31b2eab80b8ba |
completed | April 1, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69cd7edc6cf081909d95859d880a4059 |
completed | April 1, 2026, 8:23 p.m. |
Created at: March 30, 2026, 9:11 p.m.