Triple
T26115815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finningley |
E658821
|
entity |
| Predicate | hasNearbyFacilityStatus |
P5648
|
FINISHED |
| Object | Doncaster Sheffield Airport closed in 2022 |
—
|
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: Doncaster Sheffield Airport closed in 2022 | Statement: [Finningley, hasNearbyFacilityStatus, Doncaster Sheffield Airport closed in 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyFacilityStatus Context triple: [Finningley, hasNearbyFacilityStatus, Doncaster Sheffield Airport closed in 2022]
-
A.
hasNearbyFacility
chosen
Indicates that one entity is located close to or in the vicinity of a particular facility.
-
B.
hasFacilityStatusFor
Indicates that an entity has a particular operational or condition status assigned to a specific facility.
-
C.
hasNearbyBay
Indicates that one entity is located close to or adjacent to a bay associated with the other entity.
-
D.
hasFacilityLocation
Indicates that an entity possesses or is associated with a facility situated at a specific location.
-
E.
hasNearbyInfrastructureType
Indicates that an entity is located close to infrastructure of a specified type.
- 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_69ee5bc20298819099a42be042eb2349 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 26, 2026, 8:05 p.m.