Triple
T7718398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jefferson City Memorial Airport |
E174944
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | JEF |
E684390
|
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: JEF | Statement: [Jefferson City Memorial Airport, FAAcode, JEF]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: JEF Context triple: [Jefferson City Memorial Airport, FAAcode, JEF]
-
A.
JEF
chosen
JEF is the IATA airport code for Jefferson City Memorial Airport, a public airport serving Jefferson City, Missouri.
-
B.
Jef
"Jef" is a melancholic chanson by Belgian singer-songwriter Jacques Brel that portrays compassion and solidarity toward a downtrodden friend.
-
C.
JEFF
JEFF is the station code used by SEPTA for Jefferson Station, a major regional rail hub in Center City Philadelphia.
-
D.
Jeffe
Jeffe is an alternative spelling variant of the given name Jeff, typically used as a personal name.
-
E.
JFA
JFA is the governing body responsible for overseeing and organizing football activities and competitions in Jordan.
- 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_69c6995c463c8190a14458036249d419 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c702ebb7448190ae8d47fe0cbb0907 |
completed | March 27, 2026, 10:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8be2b1c5c8190b80029ab6b8b9a3f |
completed | March 29, 2026, 5:52 a.m. |
Created at: March 27, 2026, 4:05 p.m.