Triple
T27291575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 13R/31L |
E688640
|
entity |
| Predicate | hasFAAField |
P174250
|
FINISHED |
| Object | NFL |
—
|
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: NFL | Statement: [Runway 13R/31L, hasFAAField, NFL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFAAField Context triple: [Runway 13R/31L, hasFAAField, NFL]
-
A.
has FAA LID
Indicates that an entity (typically an airport or aviation facility) is assigned a specific FAA Location Identifier code.
-
B.
isInFAARegistry
Indicates that an aircraft or related entity is officially recorded and recognized in the Federal Aviation Administration’s (FAA) registry.
-
C.
containsAirfield
Indicates that a location or area includes at least one airfield within its boundaries.
-
D.
isInFAARegion
Indicates that one entity (typically a location, airspace, or facility) lies within the jurisdictional area or region defined by the FAA (Federal Aviation Administration).
-
E.
FAAcode
Indicates that an entity (such as an airport or facility) is associated with a specific identifying code assigned by the Federal Aviation Administration (FAA).
- 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_69ef355a96308190a2bed991525fb278 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6bcc425588190afd0dceba43ed79f |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
| PDg | Predicate description generation | batch_69f6bbf5a8288190ae170bcbe8ab65cf |
completed | May 3, 2026, 3:07 a.m. |
Created at: April 27, 2026, 11:15 a.m.