Triple
T34650772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Πύρρος |
E889829
|
entity |
| Predicate | συμμετείχεΣεΜάχη |
P76408
|
FINISHED |
| Object | Μάχη της Βενεβέντου (275 π.Χ.) |
—
|
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: Μάχη της Βενεβέντου (275 π.Χ.) | Statement: [Πύρρος, συμμετείχεΣεΜάχη, Μάχη της Βενεβέντου (275 π.Χ.)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: συμμετείχεΣεΜάχη Context triple: [Πύρρος, συμμετείχεΣεΜάχη, Μάχη της Βενεβέντου (275 π.Χ.)]
-
A.
battleParticipated
chosen
Indicates that an entity took part in a specific battle as a combatant or participant.
-
B.
battledIn
Indicates that two or more entities engaged in a battle or conflict that took place at a specific location or during a particular event.
-
C.
foughtAs
Indicates that an entity participated in a conflict or war in the capacity, role, or identity specified by another entity.
-
D.
battleWasPartOf
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_69f349d825c88190bfc6170ac9281260 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 2:04 a.m.