Triple
T26618633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Geonosis |
E668132
|
entity |
| Predicate | commanderForSide2 |
P68449
|
FINISHED |
| Object | Count Dooku |
—
|
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: Count Dooku | Statement: [Battle of Geonosis, commanderForSide2, Count Dooku]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commanderForSide2 Context triple: [Battle of Geonosis, commanderForSide2, Count Dooku]
-
A.
commanderForSide
Indicates that an entity serves as the military or strategic leader for a particular side or faction in a conflict or competition.
-
B.
commandersSide
Indicates that one entity is on the same side, faction, or team as the commander in a conflict or competitive context.
-
C.
commandedSide
Indicates that one entity served as the commanding side or force in relation to another entity, typically within a conflict, operation, or hierarchical command structure.
-
D.
commandedBySide
Indicates that an action, unit, or operation is under the authority or control of a specified side or faction.
-
E.
sideCommander
chosen
Indicates that an entity serves as the commanding officer or leader in charge of a particular side or faction in a conflict, operation, or organization.
- 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_69ee9cfe16088190a3dddd68e3c7b1ea |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 27, 2026, 2:20 a.m.