Triple
T34650770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Πύρρος |
E889829
|
entity |
| Predicate | κέρδισεΜάχη |
P4779
|
FINISHED |
| Object | Μάχη του Ηρακλείου (280 π.Χ.) |
—
|
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: Μάχη του Ηρακλείου (280 π.Χ.) | Statement: [Πύρρος, κέρδισεΜάχη, Μάχη του Ηρακλείου (280 π.Χ.)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: κέρδισεΜάχη Context triple: [Πύρρος, κέρδισεΜάχη, Μάχη του Ηρακλείου (280 π.Χ.)]
-
A.
defeat
Indicates that one entity wins against and overcomes another in a contest, conflict, or competition.
-
B.
victoryIn
chosen
Indicates that one entity achieves a win or success in a specific contest, event, or competitive context involving another entity.
-
C.
resultOfMilitaryCampaign
Indicates that one event, condition, or outcome occurs as a direct consequence of a specified military campaign.
-
D.
ключевоеСражение
Indicates a battle that is decisive or pivotal in determining the outcome of a larger conflict or war.
-
E.
resultOfBattle
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
- 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_69f722c27e1c819098f67081bc0764b3 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:04 a.m.