Triple
T8185833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RAF Watnall |
E191179
|
entity |
| Predicate | controlledUnit |
P62265
|
FINISHED |
| Object | fighter squadrons of No. 12 Group RAF |
—
|
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: fighter squadrons of No. 12 Group RAF | Statement: [RAF Watnall, controlledUnit, fighter squadrons of No. 12 Group RAF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlledUnit Context triple: [RAF Watnall, controlledUnit, fighter squadrons of No. 12 Group RAF]
-
A.
controlUnitType
Indicates the specific kind or category of control unit associated with or assigned to an entity.
-
B.
managementUnitOf
chosen
Indicates that one entity serves as the administrative or managerial unit responsible for overseeing or controlling another entity.
-
C.
componentUnit
Indicates that one entity functions as a constituent or sub-unit that forms part of a larger composite entity.
-
D.
coreUnitType
Indicates that one entity is classified as the primary or fundamental type/category to which another entity (a core unit) belongs.
-
E.
autonomousUnit
Indicates that an entity functions as an independent, self-governing unit capable of operating without external control.
- 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_69ca82c5b6948190a583c096fb0a6c71 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4c52407c8190bd366fce6d4e02cd |
completed | March 31, 2026, 4:23 a.m. |
| PD | Predicate disambiguation | batch_69cb36a7952481908f34e3e82f375a84 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:41 p.m.