Triple
T9445149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucius Cornelius Scipio Asiaticus |
E227744
|
entity |
| Predicate | resultOfBattleOfMagnesia |
P19109
|
FINISHED |
| Object | Roman victory |
—
|
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: Roman victory | Statement: [Lucius Cornelius Scipio Asiaticus, resultOfBattleOfMagnesia, Roman victory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfBattleOfMagnesia Context triple: [Lucius Cornelius Scipio Asiaticus, resultOfBattleOfMagnesia, Roman victory]
-
A.
resultOfBattle
chosen
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
-
B.
RomanVictory
Indicates that the Romans achieved a successful military outcome over their opponents.
-
C.
primaryByzantineForces
Indicates that the referenced forces constitute the main or principal military contingent of the Byzantine side in a given context or engagement.
-
D.
secondDacianWar
Indicates that an entity participates in, is associated with, or is relevant to the historical event known as the Second Dacian War.
-
E.
resultOfGallipoliCampaign
Indicates the outcome or consequence that directly followed from the Gallipoli Campaign.
- 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_69ca843884488190ad6cbe0153088234 |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7f32aee88190a43573f97fa1e49d |
completed | April 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69cca5596ffc819097e9c8eefd4ef9b8 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:51 p.m.