Triple
T31027549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Fombio |
E790621
|
entity |
| Predicate | primaryCommanderFrench |
P19844
|
FINISHED |
| Object | Napoleon Bonaparte |
E1341
|
NE FINISHED |
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: Napoleon Bonaparte | Statement: [Battle of Fombio, primaryCommanderFrench, Napoleon Bonaparte]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCommanderFrench Context triple: [Battle of Fombio, primaryCommanderFrench, Napoleon Bonaparte]
-
A.
FrenchCommander
chosen
Indicates that an entity serves as a military commander associated with France.
-
B.
fleetCommander (French)
Indicates that one entity serves as the commanding officer in charge of a fleet associated with another entity.
-
C.
frenchCommanderTitle
Indicates that the subject holds or is referred to by a military or naval command rank or title within a French context.
-
D.
commanderFrancoSpanish
Indicates that an entity serves as a commander of combined Franco-Spanish forces or operations.
-
E.
wasCommandantOf
Indicates that one entity served as the commandant (chief commanding officer) of another entity, typically a military unit, institution, or facility.
- F. None of above.
Provenance (4 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_69f224c97a788190b5da1ead6038a74e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a036fb4650c81908df9b9ec8ed8594b |
completed | May 12, 2026, 6:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a29389d7e748190bdcb1594f7dc5753 |
completed | June 10, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_6a036f64dc648190a31cf944d3ea0f7d |
completed | May 12, 2026, 6:20 p.m. |
Created at: April 29, 2026, 8:58 p.m.