Triple
T27189712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Scapezzano |
E683438
|
entity |
| Predicate | hasCommanderForNeapolitanForces |
P1197
|
FINISHED |
| Object | Joachim Murat |
—
|
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: Joachim Murat | Statement: [Battle of Scapezzano, hasCommanderForNeapolitanForces, Joachim Murat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommanderForNeapolitanForces Context triple: [Battle of Scapezzano, hasCommanderForNeapolitanForces, Joachim Murat]
-
A.
commanderForItaly
Indicates that a person serves or served as a military or strategic commander on behalf of Italy.
-
B.
commanderForSardinia
Indicates that one entity serves as the military or naval commander responsible for Sardinia.
-
C.
commanderForPiedmontSardinia
Indicates that one entity served as a military commander on behalf of, or in the service of, the state of Piedmont-Sardinia.
-
D.
hasCommander
chosen
Indicates that one entity serves as the commanding officer or leader of another entity.
-
E.
hasCommandant
Indicates that an entity is under the authority or leadership of a specific commandant.
- 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_69eefad140408190b8586fdebcf9af46 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fed09a12648190affcd9bacf7ca275 |
completed | May 9, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69fecf91d6f481908deb60c965c433ed |
completed | May 9, 2026, 6:09 a.m. |
Created at: April 27, 2026, 9:32 a.m.