Triple
T23593935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 148 Squadron RAF |
E582560
|
entity |
| Predicate | operationRange |
P5433
|
FINISHED |
| Object | long‑range |
—
|
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: long‑range | Statement: [No. 148 Squadron RAF, operationRange, long‑range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationRange Context triple: [No. 148 Squadron RAF, operationRange, long‑range]
-
A.
operationalRange
Indicates the span of conditions (such as distance, time, or environment) within which a system, device, or process can function effectively and safely.
-
B.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
C.
rangeCapability
chosen
Indicates the maximum distance or extent over which an entity can effectively operate, function, or exert its effect.
-
D.
launchRangeOperator
Indicates the entity that operates or manages the launch range used for a launch event or launch vehicle.
-
E.
coreRange
Indicates the primary spatial or temporal extent within which an entity, phenomenon, or relationship is predominantly present or valid.
- 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_69e248f9e0a08190814772847003b1ff |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b08d63dc81908c092a87cf61f2b9 |
completed | April 29, 2026, 7:17 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:42 p.m.