Triple
T26273617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RAF Finningley |
E660498
|
entity |
| Predicate | usedAsRAFStationFrom |
P99165
|
FINISHED |
| Object | 1936 |
—
|
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: 1936 | Statement: [RAF Finningley, usedAsRAFStationFrom, 1936]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsRAFStationFrom Context triple: [RAF Finningley, usedAsRAFStationFrom, 1936]
-
A.
usedAsRAFBase
chosen
Indicates that a location or facility has been used as a base of operations by the Royal Air Force.
-
B.
openedAsRAFStation
Indicates that a facility or location was initially established and began operation as a Royal Air Force (RAF) station.
-
C.
isStationOf
Indicates that a given location functions as a station (e.g., transport or service hub) associated with or serving a particular system, line, route, or organization.
-
D.
closedAsRAFStation
Indicates that a facility or location ceased operations specifically in its role as a Royal Air Force (RAF) station.
-
E.
hasStationAt
Indicates that an entity maintains or operates a station located at a specified place.
- 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_69ee812960d081909cff6085cc9fa3a6 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 26, 2026, 9:53 p.m.