Triple
T27189711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Scapezzano |
E683438
|
entity |
| Predicate | hasCommanderForAustrianForces |
P49085
|
FINISHED |
| Object | Frederick Bianchi |
—
|
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: Frederick Bianchi | Statement: [Battle of Scapezzano, hasCommanderForAustrianForces, Frederick Bianchi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommanderForAustrianForces Context triple: [Battle of Scapezzano, hasCommanderForAustrianForces, Frederick Bianchi]
-
A.
combatantCommanderAustria
chosen
Indicates that the referenced entity served as a military commander for Austria in a particular conflict or combat situation.
-
B.
notableCommanderAustriaHungary
Indicates that an individual served as a notable military commander for Austria-Hungary.
-
C.
commanderHungarianSide
Indicates that the subject served as a commander on the Hungarian side in a conflict or military engagement.
-
D.
AustrianArmy
Indicates that an entity is the Austrian Army or is serving as part of the Austrian Army in a given context.
-
E.
monarchOfAustriaDuringWar
Indicates that a person held the position of monarch of Austria during a specified war or military conflict.
- 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_69feced53a7c819098ec474fb7d514b0 |
completed | May 9, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69fecd9cd5288190aac8b4e04a7ee78e |
completed | May 9, 2026, 6:01 a.m. |
Created at: April 27, 2026, 9:32 a.m.