Triple
T1750339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fighter Wing 52 |
E38424
|
entity |
| Predicate | subUnitType |
P7150
|
FINISHED |
| Object | Gruppe |
—
|
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: Gruppe | Statement: [Fighter Wing 52, subUnitType, Gruppe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subUnitType Context triple: [Fighter Wing 52, subUnitType, Gruppe]
-
A.
subunitType
chosen
Indicates that one entity is a specific kind or classification of subunit within the structure or composition of another entity.
-
B.
subunitOf
Indicates that one entity functions as a component or smaller part within the structure or organization of another, larger entity.
-
C.
subsidiaryUnit
Indicates that one organizational unit functions as a subordinate or dependent division of another, higher-level unit.
-
D.
basedUnitType
Indicates that one unit is defined or derived in terms of another underlying (base) unit type.
-
E.
typeOfUnit
Indicates that one entity specifies the kind or category of measurement unit that the other entity belongs to.
- 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_69a8862bdb2081908aefe831c8aa8017 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69aba6a63f588190b53b39c6b97d74f4 |
completed | March 7, 2026, 4:16 a.m. |
| PD | Predicate disambiguation | batch_69aa61c7ef4c8190abec87c96a787d82 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.