Triple
T2996128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RAF Honington |
E81069
|
entity |
| Predicate | hasFireStation |
P44903
|
FINISHED |
| Object | military fire and rescue service |
—
|
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: military fire and rescue service | Statement: [RAF Honington, hasFireStation, military fire and rescue service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFireStation Context triple: [RAF Honington, hasFireStation, military fire and rescue service]
-
A.
hasPoliceStationsIn
Indicates that one entity possesses, manages, or contains one or more police stations located within the area or jurisdiction of another entity.
-
B.
hasBusStation
Indicates that a place or area contains or is served by a bus station.
-
C.
hasNearbyFacility
Indicates that one entity is located close to or in the vicinity of a particular facility.
-
D.
hasLifeboatStation
Indicates that a place or facility is equipped with a lifeboat station for maritime rescue or emergency response.
-
E.
hasStationBuilding
Indicates that a station is associated with or includes a station building as part of its facilities.
- F. None of above. chosen
Provenance (4 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_69ad8b187fc8819085914d3c9ea3142d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99f481688190ae8cd1e057f9dfc7 |
completed | March 8, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69ad9615fefc8190ad96da92519cb7a3 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97ba55dc8190b6dddddfb751cf64 |
completed | March 8, 2026, 3:37 p.m. |
Created at: March 8, 2026, 2:59 p.m.