Triple
T26450759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RAF Wyton |
E665340
|
entity |
| Predicate | operatorUnit |
P17883
|
FINISHED |
| Object | No. 4 Squadron RAF |
—
|
NE NERFINISHED |
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: No. 4 Squadron RAF | Statement: [RAF Wyton, operatorUnit, No. 4 Squadron RAF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorUnit Context triple: [RAF Wyton, operatorUnit, No. 4 Squadron RAF]
-
A.
operatedUnit
Indicates that one entity functions as a unit or component that is operated or controlled by another entity.
-
B.
operatedByUnit
chosen
Indicates that an entity (such as a system, device, or facility) is run, controlled, or managed by a specific organizational unit.
-
C.
operationalUnit
Indicates that one entity functions as an operational unit (a distinct executing or managing unit) within the scope or structure defined by another entity.
-
D.
operatesUnitType
Indicates that an entity runs, manages, or controls a unit of a specified type.
-
E.
managementUnitOf
Indicates that one entity serves as the administrative or managerial unit responsible for overseeing or controlling another entity.
- 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_69ee883d5040819097dd154643005230 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: April 27, 2026, 12:05 a.m.