Triple
T35312191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skyhaven Airport |
E1019801
|
entity |
| Predicate | hasFAALocationIdentifier |
P195740
|
FINISHED |
| Object | RCM |
—
|
NE NERFINISHED |
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: RCM | Statement: [Skyhaven Airport, hasFAALocationIdentifier, RCM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFAALocationIdentifier Context triple: [Skyhaven Airport, hasFAALocationIdentifier, RCM]
-
A.
hasLocationRole
Indicates that an entity holds or plays a specific role in relation to a particular location (e.g., origin, destination, storage site, or operational area).
-
B.
hasNationalLocationCode
Indicates that an entity is associated with a specific national location code that identifies its location within a country’s coding system.
-
C.
hasLocationComponent
Indicates that something includes, is associated with, or is composed of a specific location-related part or element.
-
D.
hasIdentifierSystem
Indicates that an entity is associated with a particular system or scheme used to assign and manage its identifiers.
-
E.
hasICAOLocationIndicator
Indicates that an entity is associated with a specific ICAO location indicator code, typically identifying an airport or aerodrome in the ICAO system.
- 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
| PDg | Predicate description generation | batch_69fde49953c481909ac352ab36fa9ff2 |
completed | May 8, 2026, 1:26 p.m. |
Created at: May 3, 2026, 4:03 p.m.