Triple
T29051840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Salisbury |
E735278
|
entity |
| Predicate | hasAirportWithin |
P40417
|
FINISHED |
| Object | Parafield Airport |
—
|
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: Parafield Airport | Statement: [City of Salisbury, hasAirportWithin, Parafield Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAirportWithin Context triple: [City of Salisbury, hasAirportWithin, Parafield Airport]
-
A.
hasAirportWithinJurisdiction
Indicates that a governing authority or administrative region has legal or administrative control over an airport located within its boundaries.
-
B.
hasAirportAccessTo
Indicates that one location or entity has direct access to another via an airport connection or service.
-
C.
airportLocatedWithin
chosen
Indicates that an airport is geographically situated inside the boundaries of a specified area or region.
-
D.
hasRegionalAirport
Indicates that a place or region possesses or is served by a regional airport.
-
E.
basedInAirport
Indicates that an entity has its primary location, operations, or headquarters situated at a specific airport.
- 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 10:08 a.m.