Triple
T38436601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 918th Bomb Group |
E903961
|
entity |
| Predicate | hasFictionalCommanderRank |
P202507
|
FINISHED |
| Object | brigadier 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: brigadier general | Statement: [918th Bomb Group, hasFictionalCommanderRank, brigadier general]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalCommanderRank Context triple: [918th Bomb Group, hasFictionalCommanderRank, brigadier general]
-
A.
hasCommanderRank
Indicates that an entity holds the military or organizational rank of commander within a specified hierarchy or context.
-
B.
hasFictionalOfficerRankStructure
Indicates that an entity employs a rank hierarchy for officers that is invented or fictional rather than based on real-world military or organizational rank systems.
-
C.
rankOfNotableCommander
Indicates the military or organizational rank held by a notable commander associated with an entity.
-
D.
hasRankForCommandant
Indicates that an entity holds the specific rank required to serve as a commandant.
-
E.
hasDanishCommanderRank
Indicates that an entity holds or is assigned a military commander rank within the Danish armed forces.
- F. None of above. chosen
Provenance (4 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a008b8938608190adaccbd720111a18 |
completed | May 10, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_6a008b24baac8190baaaf50c2e9cc6bd |
completed | May 10, 2026, 1:41 p.m. |
| PDg | Predicate description generation | batch_6a008b8870b481909c1a2707a7b06d49 |
completed | May 10, 2026, 1:43 p.m. |
Created at: May 3, 2026, 4:31 p.m.