Triple
T8924406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gnaeus Pompeius (son of Pompey) |
E212503
|
entity |
| Predicate | outcomeOfBattleOfMunda |
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: [Gnaeus Pompeius (son of Pompey), outcomeOfBattleOfMunda, defeat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outcomeOfBattleOfMunda Context triple: [Gnaeus Pompeius (son of Pompey), outcomeOfBattleOfMunda, defeat]
-
A.
RomanVictory
Indicates that the Romans achieved a successful military outcome over their opponents.
-
B.
resultOfBattle
chosen
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
-
C.
secondDacianWar
Indicates that an entity participates in, is associated with, or is relevant to the historical event known as the Second Dacian War.
-
D.
firstDacianWar
Indicates the relationship in which an event or context is part of, refers to, or occurs during the First Dacian War.
-
E.
battleWasPartOf
Indicates that a specific battle occurred as a component or phase within a larger military campaign, war, or conflict.
- 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_69ca839481d48190b42b037e0d0f636c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66547de881909ea9bfd104b32893 |
completed | April 1, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed0ef3c81908cc69eac852ee12a |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:57 p.m.