Triple
T10942277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Handley Page Hampden |
E258501
|
entity |
| Predicate | operatedByUnitType |
P17883
|
FINISHED |
| Object | RAF Bomber Command squadrons |
—
|
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: RAF Bomber Command squadrons | Statement: [Handley Page Hampden, operatedByUnitType, RAF Bomber Command squadrons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedByUnitType Context triple: [Handley Page Hampden, operatedByUnitType, RAF Bomber Command squadrons]
-
A.
operatedByUnit
chosen
Indicates that an entity (such as a system, device, or facility) is run, controlled, or managed by a specific organizational unit.
-
B.
operatesUnitType
Indicates that an entity runs, manages, or controls a unit of a specified type.
-
C.
operatedByCompany
Indicates that an entity is run, managed, or controlled by a specific company.
-
D.
operatesBy
Indicates that an entity performs its function, action, or process through the use or application of another entity (e.g., a method, mechanism, or principle).
-
E.
operatedAs
Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
- 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_69d6aa8769b4819082bfe5e61b9017f0 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770c33a7c8190b3347944f68ee431 |
completed | April 9, 2026, 9:26 a.m. |
| PD | Predicate disambiguation | batch_69d72e816a98819096d6c10dfb88a66a |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:23 p.m.