Triple
T24306479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of Saint-Cloud |
E612548
|
entity |
| Predicate | militaryCommanderPresent |
P1197
|
FINISHED |
| Object | Napoleon Bonaparte |
—
|
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: Napoleon Bonaparte | Statement: [Council of Saint-Cloud, militaryCommanderPresent, Napoleon Bonaparte]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryCommanderPresent Context triple: [Council of Saint-Cloud, militaryCommanderPresent, Napoleon Bonaparte]
-
A.
hasCommander
chosen
Indicates that one entity serves as the commanding officer or leader of another entity.
-
B.
hasCommandant
Indicates that an entity is under the authority or leadership of a specific commandant.
-
C.
isMilitaryCommand
Indicates that one entity holds formal military authority or command over another entity or group.
-
D.
hasCommanderRank
Indicates that an entity holds the military or organizational rank of commander within a specified hierarchy or context.
-
E.
commanderOnBoard
Indicates that a specific individual holds the role of commanding officer on a particular vehicle, vessel, or craft during its operation.
- 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_69e2d7d91bb48190bc5377d17a85fb21 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292272af88190b9c23615adbac911 |
completed | April 29, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 1:30 a.m.