Triple
T14442312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J. F. Mitchell Airport |
E358111
|
entity |
| Predicate | hasApproachOverWater |
P114293
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [J. F. Mitchell Airport, hasApproachOverWater, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproachOverWater Context triple: [J. F. Mitchell Airport, hasApproachOverWater, true]
-
A.
hasDestinationSea
Indicates that something is directed or travels toward a sea as its endpoint or target location.
-
B.
navigatedOcean
Indicates that an entity traveled or steered a vessel across or through an ocean.
-
C.
hasSeaVoyage
Indicates that an entity undertakes, includes, or is associated with a journey or travel conducted by sea.
-
D.
hasNearbyWatersUsedBy
Indicates that a body of water located near an entity is utilized or accessed by another specified entity.
-
E.
navigatesWaterBody
Indicates that an entity moves through or across a body of water as a means of travel or operation.
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de915d28ec81909e72124e9dd67bfb |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
| PDg | Predicate description generation | batch_69de5fb4de14819092acdecbd201d672 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:18 a.m.