Triple
T16488101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Inspector of the Bundeswehr |
E400498
|
entity |
| Predicate | positionHolderRank |
P7155
|
FINISHED |
| Object | Lieutenant General |
—
|
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: Lieutenant General | Statement: [Army Inspector of the Bundeswehr, positionHolderRank, Lieutenant General]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionHolderRank Context triple: [Army Inspector of the Bundeswehr, positionHolderRank, Lieutenant General]
-
A.
rankingPositions
Indicates the ordered placement or level assigned to entities within a ranking or hierarchy.
-
B.
roleInRanking
Indicates that an entity holds a specific position or function within a particular ranking or ordered list.
-
C.
rankHeldByPost
chosen
Indicates that a particular organizational post or position is associated with, or carries, a specific rank.
-
D.
lastHolderRank
Indicates the rank or position held by the most recent entity that possessed or held a given item, title, or role.
-
E.
positionHeld
Indicates that an entity occupies or has occupied a specific role, job, office, or position within an organization or context.
- 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e084f388190887dfb3f6928f506 |
completed | April 18, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:13 a.m.