Triple
T14219715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chōfu |
E352456
|
entity |
| Predicate | ChōfuAirportUsedFor |
P16381
|
FINISHED |
| Object | commuter flights to Izu Islands |
—
|
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: commuter flights to Izu Islands | Statement: [Chōfu, ChōfuAirportUsedFor, commuter flights to Izu Islands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ChōfuAirportUsedFor Context triple: [Chōfu, ChōfuAirportUsedFor, commuter flights to Izu Islands]
-
A.
appliesToAirport
Indicates that something is relevant, valid, or specifically intended for use at a particular airport.
-
B.
hasAirportRelatedFunction
Indicates that something performs a role, service, or activity specifically related to the operation, support, or functioning of an airport.
-
C.
airportServesAs
chosen
Indicates that an airport functions in a particular role or capacity (such as primary, secondary, or hub) for a specified area, organization, or service.
-
D.
basedInAirport
Indicates that an entity has its primary location, operations, or headquarters situated at a specific airport.
-
E.
servesAirport
Indicates that a transportation service or route provides access to and operates for a particular 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_69d8278a06e481908b5d6af0a8afe737 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de621258d4819085f358cd2cf109e4 |
completed | April 14, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69de05bcd7d48190a4848d9320404aa6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:06 a.m.