Triple
T19456898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army of the Ebro |
E486756
|
entity |
| Predicate | resultOfMainOffensive |
P15636
|
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: [Army of the Ebro, resultOfMainOffensive, defeat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfMainOffensive Context triple: [Army of the Ebro, resultOfMainOffensive, defeat]
-
A.
offensiveStrength
Indicates the degree or capacity of an entity to carry out effective attacks or aggressive actions against an opponent.
-
B.
offensiveOperation
Indicates an action or campaign in which a party actively initiates hostile or military measures against an opponent.
-
C.
tacticalOutcome
chosen
Indicates the specific result or consequence produced by a particular tactic or tactical action in a given situation.
-
D.
offensiveForce
Indicates the use or application of aggressive or attacking power or violence by one entity against another.
-
E.
offensiveStrategy
Indicates a strategic approach focused on attacking or aggressively advancing against an opponent.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633c4088881908f23f25a82a513f6 |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.