Triple
T6896212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hahajima |
E159375
|
entity |
| Predicate | hasNoAirport |
P73998
|
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: [Hahajima, hasNoAirport, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoAirport Context triple: [Hahajima, hasNoAirport, true]
-
A.
hasNoRegularCommercialAirlineService
Indicates that a location or facility is not served by any scheduled, routine commercial airline flights.
-
B.
hasRegionalAirport
Indicates that a place or region possesses or is served by a regional airport.
-
C.
hasEndpointAirport
Indicates that something, such as a route or flight, has a specific airport as one of its terminal endpoints.
-
D.
hasInternationalAirport
Indicates that a place possesses an airport that handles international flights and services cross-border air traffic.
-
E.
hasCoreAirport
Indicates that one entity designates another entity as its primary or central airport within a given context or network.
- 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_69c6883822e0819091e321526f20ae0a |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d95ae3f88190b7f5d440f90ae9f9 |
completed | March 27, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b7681481909ec50509b19fcf81 |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8c48ba48190b8d3aa7b8d22816b |
completed | March 27, 2026, 7:21 p.m. |
Created at: March 27, 2026, 2:24 p.m.