Triple
T23628651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KDHN |
E583543
|
entity |
| Predicate | isInFAARegistry |
P153332
|
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: [KDHN, isInFAARegistry, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInFAARegistry Context triple: [KDHN, isInFAARegistry, yes]
-
A.
aircraftRegistration
Indicates that an aircraft is assigned a specific official registration identifier or code.
-
B.
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).
-
C.
usedByAircraftRegisteredIn
Indicates that something (such as equipment, a system, or a facility) is utilized by aircraft that are registered in a specified jurisdiction or registry.
-
D.
aircraftRegistrationInvolved
Indicates that a specific aircraft registration is involved in, associated with, or affected by a particular event, action, or record.
-
E.
FAAUnGroundingDate
Indicates the date on which the FAA officially lifts a grounding order and allows the affected aircraft or operation to resume flying.
- 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_69e248fc8d74819091bd5baef2f36f6f |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b1e5ae80819085c417e8d81b74ad |
completed | April 29, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f138b8c9248190b059bc38a9a50958 |
completed | April 28, 2026, 10:46 p.m. |
Created at: April 17, 2026, 6:46 p.m.