Triple
T30111127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helston |
E765277
|
entity |
| Predicate | hasNearbyRAFStation |
P5648
|
FINISHED |
| Object | RNAS Culdrose |
—
|
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: RNAS Culdrose | Statement: [Helston, hasNearbyRAFStation, RNAS Culdrose]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyRAFStation Context triple: [Helston, hasNearbyRAFStation, RNAS Culdrose]
-
A.
hasStationNear
Indicates that one entity has a station located in close proximity to another entity.
-
B.
hasNearbyFacility
chosen
Indicates that one entity is located close to or in the vicinity of a particular facility.
-
C.
hasFireStation
Indicates that a location or area contains or is served by a fire station.
-
D.
hasNearbyRailwayStation
Indicates that a railway station is located within a short or convenient distance from the referenced entity.
-
E.
operatorOfNearbyStation
Indicates that an entity operates or manages a station located in close geographic proximity to another referenced 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe91383a1c81909266e40c3c3ede6c |
completed | May 9, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69fe8fde094081908f0f121664fbb5c7 |
completed | May 9, 2026, 1:37 a.m. |
Created at: April 29, 2026, 7:10 p.m.