Triple
T21407880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French field army under Vendôme |
E528085
|
entity |
| Predicate | commandRankOfCommander |
P90400
|
FINISHED |
| Object | Marshal of France |
—
|
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: Marshal of France | Statement: [French field army under Vendôme, commandRankOfCommander, Marshal of France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandRankOfCommander Context triple: [French field army under Vendôme, commandRankOfCommander, Marshal of France]
-
A.
governmentCommanderRank
Indicates that an individual holds a specific rank within a government’s command or leadership hierarchy.
-
B.
commanderInChiefRank
Indicates that an entity holds the highest-ranking leadership position over a military or armed forces organization.
-
C.
hasCommanderRank
Indicates that an entity holds the military or organizational rank of commander within a specified hierarchy or context.
-
D.
hasRankForCommandant
Indicates that an entity holds the specific rank required to serve as a commandant.
-
E.
rankOfNotableCommander
chosen
Indicates the military or organizational rank held by a notable commander associated with an entity.
- 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_69e0b520ee3c8190abddbee7e37e834c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b1b25fa48190a968f482beb8377a |
completed | April 22, 2026, 11:32 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:32 p.m.