Triple
T18192536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles de Bourbon |
E435573
|
entity |
| Predicate | roleInItalianWars |
P108011
|
FINISHED |
| Object | commander of imperial forces in Italy |
—
|
LITERAL 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: commander of imperial forces in Italy | Statement: [Charles de Bourbon, roleInItalianWars, commander of imperial forces in Italy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInItalianWars Context triple: [Charles de Bourbon, roleInItalianWars, commander of imperial forces in Italy]
-
A.
strategicRoleDuringWar
Indicates that an entity served a particular strategic function or importance during a specific war or armed conflict.
-
B.
roleInWarOrConflict
chosen
Indicates the specific function, position, or involvement an entity has within a particular war or conflict.
-
C.
roleInPunicWars
Indicates the specific involvement, function, or position an entity had in the events or campaigns of the Punic Wars.
-
D.
notableBattleRole
Indicates the specific role or function an entity played in a notable or historically significant battle.
-
E.
roleInTimeWar
Indicates that an entity held a specific role or function during the period or events referred to as the Time War.
- 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e0d05974819094b4a50d081be881 |
completed | April 19, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69e4331e92408190ad607ba4956a3897 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:31 a.m.