Triple
T17644643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Benevento |
E429323
|
entity |
| Predicate | outcomeForManfred |
P128373
|
FINISHED |
| Object | loss of throne |
—
|
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: loss of throne | Statement: [Battle of Benevento, outcomeForManfred, loss of throne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outcomeForManfred Context triple: [Battle of Benevento, outcomeForManfred, loss of throne]
-
A.
outcomeForMen
Indicates the specific result, effect, or consequence that an event, action, or condition has for men.
-
B.
resultForFriedrichFlick
Indicates the outcome or decision rendered in relation to Friedrich Flick, such as a verdict, ruling, or final result concerning him.
-
C.
outcomeOf
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
D.
outcomeForStralsund
Indicates the result, consequence, or effect that an event, action, or situation has specifically for Stralsund.
-
E.
outcomeForPrussia
Indicates the result or consequence that an event, action, or situation has specifically for Prussia.
- 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_69d889e2c2608190b762e76d9b2262f1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46de7da4881908d67f447910dba2f |
completed | April 19, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69e3cddc87188190ac2f049b86038676 |
completed | April 18, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 6:04 a.m.