Triple
T31001829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Chiclana |
E789959
|
entity |
| Predicate | combatantCommanderSide2 |
P32311
|
FINISHED |
| Object | Marshal Victor |
—
|
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: Marshal Victor | Statement: [Battle of Chiclana, combatantCommanderSide2, Marshal Victor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatantCommanderSide2 Context triple: [Battle of Chiclana, combatantCommanderSide2, Marshal Victor]
-
A.
combatant2Commander
chosen
Indicates that a combatant serves under the authority or command of a specific commander.
-
B.
commandersSide
Indicates that one entity is on the same side, faction, or team as the commander in a conflict or competitive context.
-
C.
opposingCommanderSide
Indicates that one commander is on the opposing or enemy side relative to another commander in a conflict or confrontation.
-
D.
opponentCommanderSide
Indicates that one commander is positioned on the opposing side relative to another commander in a conflict or competitive scenario.
-
E.
overallCommanderSide
Indicates that one entity serves as the primary commanding side or overarching leadership faction in relation to another entity within a conflict or organizational structure.
- 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_69f224c65a348190baaed1c01a29900c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 29, 2026, 8:56 p.m.