Triple
T13294439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drake Field |
E316643
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | FYV |
E1033096
|
NE 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: FYV | Statement: [Drake Field, FAAcode, FYV]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FYV Context triple: [Drake Field, FAAcode, FYV]
-
A.
FYV
chosen
FYV is the IATA airport code for Drake Field, a public airport serving Fayetteville, Arkansas.
-
B.
FY
FY is a UK postcode area covering parts of the Fylde coast in Lancashire, including towns such as Blackpool and Thornton-Cleveleys.
-
C.
YV
YV is the IATA airline designator used to identify Mesa Airlines in flight schedules and ticketing systems.
-
D.
FV
FV is the IATA airline designator assigned to Rossiya Airlines, a Russian carrier based in Saint Petersburg.
-
E.
FVEY
FVEY is an abbreviation for the Five Eyes, an intelligence alliance comprising Australia, Canada, New Zealand, the United Kingdom, and the United States that cooperates on signals intelligence and security matters.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99079c8508190b6208db9affcbc0e |
completed | April 11, 2026, 12:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f71f247e2081908759c40c0023c7ae |
completed | May 3, 2026, 10:10 a.m. |
Created at: April 9, 2026, 9:28 p.m.