Triple
T11162521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conradin |
E264072
|
entity |
| Predicate | battleOutcome_Battle of Tagliacozzo |
P19109
|
FINISHED |
| Object | defeat |
—
|
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: defeat | Statement: [Conradin, battleOutcome_Battle of Tagliacozzo, defeat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleOutcome_Battle of Tagliacozzo Context triple: [Conradin, battleOutcome_Battle of Tagliacozzo, defeat]
-
A.
battleWasPartOf
Indicates that a specific battle occurred as a component or phase within a larger military campaign, war, or conflict.
-
B.
battleOccurredOn
Indicates that a specific battle took place at or on a particular location or date.
-
C.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
-
D.
resultOfBattle
chosen
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
-
E.
battleAlsoKnownAs
Indicates that a particular battle is known by an alternative name or names.
- 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8832fe88190a74d81f9ed547baa |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75cec26fc8190a5497d186306f935 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.