Triple
T10237432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IJ |
E243500
|
entity |
| Predicate | nearbyAirportAccess |
P92912
|
FINISHED |
| Object | Amsterdam Airport Schiphol via North Sea Canal route |
—
|
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: Amsterdam Airport Schiphol via North Sea Canal route | Statement: [IJ, nearbyAirportAccess, Amsterdam Airport Schiphol via North Sea Canal route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyAirportAccess Context triple: [IJ, nearbyAirportAccess, Amsterdam Airport Schiphol via North Sea Canal route]
-
A.
nearbyAirportCorridor
Indicates that an airport corridor is located close to or within a short distance of a given reference location or area.
-
B.
nearbyAirportTerminal
Indicates that one airport terminal is located close to another airport terminal in physical space.
-
C.
nearestAirport
Indicates that one airport is the closest in distance to a given location or entity compared to all other airports.
-
D.
airportLocatedNear
Indicates that an airport is situated close to a specified place or geographic feature.
-
E.
distanceToAirport
Indicates the measured distance between a given location and the nearest or specified airport.
- 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_69d381b0f97c819085c9b45799a5fb7c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d23b620c8190b8a72d0eb0d16b93 |
completed | April 7, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69d4d1e9798c8190b437d53d48554ba1 |
completed | April 7, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69d4d23a9c4c8190abece9e52879c479 |
completed | April 7, 2026, 9:45 a.m. |
Created at: April 6, 2026, 11:23 a.m.