Triple
T32162292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Medina |
E821459
|
entity |
| Predicate | sideWithHeaviestLosses |
P82956
|
FINISHED |
| Object | Republican Army of the North |
—
|
NE NERFINISHED |
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: Republican Army of the North | Statement: [Battle of Medina, sideWithHeaviestLosses, Republican Army of the North]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sideWithHeaviestLosses Context triple: [Battle of Medina, sideWithHeaviestLosses, Republican Army of the North]
-
A.
sideLost
Indicates that a particular side, party, or team was defeated or failed to win in a contest, conflict, or competition.
-
B.
sideDefeated
Indicates that one side in a conflict, competition, or contest has been beaten or overcome by another side.
-
C.
countryOfDefeatedSide
Indicates the country to which the losing or defeated side in a conflict, competition, or confrontation belongs.
-
D.
causedTerritorialLossesTo
Indicates that one entity was responsible for another entity losing control over some portion of its territory.
-
E.
militaryCasualtiesSide
chosen
Indicates the side or party in a conflict to which the recorded military casualties belong.
- 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_69f34905e098819082191a6922a6d607 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6ba1b75748190af3f7df0cd0ed2a9 |
completed | May 3, 2026, 2:59 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:32 a.m.