Triple
T25908136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Undicesima battaglia dell'Isonzo |
E652812
|
entity |
| Predicate | comandante |
P1061
|
FINISHED |
| Object | Luigi Cadorna |
—
|
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: Luigi Cadorna | Statement: [Undicesima battaglia dell'Isonzo, comandante, Luigi Cadorna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comandante Context triple: [Undicesima battaglia dell'Isonzo, comandante, Luigi Cadorna]
-
A.
commander
chosen
Indicates that one entity holds authoritative military or organizational control over another entity or group.
-
B.
hasCommandant
Indicates that an entity is under the authority or leadership of a specific commandant.
-
C.
sideCommander
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.
-
D.
commanderOnBoard
Indicates that a specific individual holds the role of commanding officer on a particular vehicle, vessel, or craft during its operation.
-
E.
combatant2Commander
Indicates that a combatant serves under the authority or command of a specific commander.
- 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_69e7ab3d3f8481909bc53ed64c06af33 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f603c15b348190a7f00745b6475b28 |
completed | May 2, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 8:27 a.m.