Triple
T25430883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FUN |
E637248
|
entity |
| Predicate | airportServesAsEmergencyLink |
P16381
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [FUN, airportServesAsEmergencyLink, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airportServesAsEmergencyLink Context triple: [FUN, airportServesAsEmergencyLink, yes]
-
A.
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.
-
B.
associatedAirportServes
Indicates that a given airport provides service to, or is used by, the associated entity (such as a city, region, or facility).
-
C.
airportLinkName
Indicates the name assigned to a transportation link or connection associated with an airport.
-
D.
airportLocationRelation
Indicates a spatial or administrative relationship specifying where an airport is located relative to a geographic area or jurisdiction.
-
E.
hasEmergencyAirstrip
Indicates that an entity possesses or includes an airstrip specifically designated and equipped for emergency use.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 21, 2026, 1:58 p.m.