Triple
T35532326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philippe de Sucy |
E1026834
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional French officer |
C66344
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: fictional French officer Context triple: [Philippe de Sucy, instanceOf, fictional French officer]
-
A.
French military leader
A French military leader is a high-ranking officer from France responsible for planning, directing, and commanding military operations and forces in defense of national interests.
-
B.
European officer
A European officer is a military or colonial administrative figure originating from a European nation, typically holding a position of authority and responsibility within an organized armed force or governing structure.
-
C.
Swiss military officer
A Swiss military officer is a commissioned leader in Switzerland’s armed forces responsible for planning, directing, and overseeing military operations, training, and personnel in accordance with Swiss defense policies and neutrality principles.
-
D.
Belgian general
A Belgian general is a high-ranking military officer from Belgium responsible for leading large military formations, developing strategic plans, and overseeing operations within the Belgian Armed Forces or in multinational contexts.
-
E.
Bavarian military officer
A Bavarian military officer is a commissioned leader from the historical Kingdom or modern state of Bavaria, responsible for commanding troops, executing military strategy, and upholding regional and national defense duties within the broader German armed forces context.
- F. None of above. chosen
Provenance (1 batch)
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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.