Triple
T16978333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FVTL |
E411871
|
entity |
| Predicate | IcaoSubregion |
P42294
|
FINISHED |
| Object | FV |
—
|
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: FV | Statement: [FVTL, IcaoSubregion, FV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IcaoSubregion Context triple: [FVTL, IcaoSubregion, FV]
-
A.
ICAORegion
Indicates that an entity is located within, associated with, or governed by a specific ICAO (International Civil Aviation Organization) region.
-
B.
associatedAirportICAOSubregion
chosen
Indicates a relationship where an airport is linked to the specific ICAO-defined subregion in which it is located or with which it is operationally associated.
-
C.
associatedAirportGeographicRegion
Indicates that an airport is located within or linked to a specific geographic region.
-
D.
associatedAirportCountrySubdivision
Indicates the specific country subdivision (such as a state, province, or region) in which the associated airport is located.
-
E.
ICAOairport
Indicates that an entity is an airport identified or classified according to the ICAO (International Civil Aviation Organization) airport coding system.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d185a9408190a991bf8a1ef694f0 |
completed | April 18, 2026, 6:46 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.