Triple
T25715485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FLYER |
E644850
|
entity |
| Predicate | usedWithIcaoCode |
P36333
|
FINISHED |
| Object | CFE |
—
|
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: CFE | Statement: [FLYER, usedWithIcaoCode, CFE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedWithIcaoCode Context triple: [FLYER, usedWithIcaoCode, CFE]
-
A.
associatedWithICAOcode
chosen
Indicates a relationship where an entity is linked to, or identified by, a specific ICAO (International Civil Aviation Organization) code.
-
B.
ICAOcode
Indicates that an entity is identified by a specific four-letter airport or aerodrome code assigned by the International Civil Aviation Organization (ICAO).
-
C.
hasIcaoAirport
Indicates that an entity is associated with an airport identified by a specific ICAO (International Civil Aviation Organization) airport code.
-
D.
ICAOEngineCode
Indicates that an engine is identified or classified by a specific ICAO (International Civil Aviation Organization) engine 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 21, 2026, 9:40 p.m.