Triple
T37075845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Konteradmiral |
E917705
|
entity |
| Predicate | comparableAirForceRank |
P95916
|
FINISHED |
| Object | Generalmajor (Luftwaffe) |
—
|
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: Generalmajor (Luftwaffe) | Statement: [Konteradmiral, comparableAirForceRank, Generalmajor (Luftwaffe)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comparableAirForceRank Context triple: [Konteradmiral, comparableAirForceRank, Generalmajor (Luftwaffe)]
-
A.
equivalentAirForceRank
chosen
Indicates that two military positions or titles correspond to the same rank level within different air forces.
-
B.
equivalentRankInUSAF
Indicates that two military ranks are considered equivalent in status or grade within the United States Air Force.
-
C.
equivalentRankRoyalAirForce
Indicates that two military ranks are considered equivalent in status or level within the Royal Air Force rank structure.
-
D.
militaryRankOfPrecedence
Indicates the relative seniority or priority order of a military rank compared to other ranks.
-
E.
equivalentRankInArmy
Indicates that two entities hold military positions considered to be of the same rank or level within their respective armies.
- 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_69f76e9771e08190a690834e3cd20654 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
Created at: May 3, 2026, 4:14 p.m.