Triple
T23966329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KU42 |
E604091
|
entity |
| Predicate | correspondsToFAAIdentifier |
P420
|
FINISHED |
| Object | U42 |
—
|
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: U42 | Statement: [KU42, correspondsToFAAIdentifier, U42]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: correspondsToFAAIdentifier Context triple: [KU42, correspondsToFAAIdentifier, U42]
-
A.
associatedWithICAOcode
Indicates a relationship where an entity is linked to, or identified by, a specific ICAO (International Civil Aviation Organization) code.
-
B.
isInFAARegistry
Indicates that an aircraft or related entity is officially recorded and recognized in the Federal Aviation Administration’s (FAA) registry.
-
C.
FAAcode
chosen
Indicates that an entity (such as an airport or facility) is associated with a specific identifying code assigned by the Federal Aviation Administration (FAA).
-
D.
aircraftRegistration
Indicates that an aircraft is assigned a specific official registration identifier or code.
-
E.
hasICAOComplement
Indicates that one entity serves as an ICAO-standard complement or additional code/information corresponding to another entity’s primary ICAO designation.
- 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_69e29543019c8190872462e593cc50b4 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d1d7fbf88190820bcfbdc237c2a3 |
completed | April 29, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:24 p.m.