Triple
T15820675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harrisburg International Airport |
E383597
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | MDT |
E1178520
|
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: MDT | Statement: [Harrisburg International Airport, FAAcode, MDT]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MDT Context triple: [Harrisburg International Airport, FAAcode, MDT]
-
A.
MDT
MDT is the stock ticker symbol for Medtronic, a leading global medical technology company specializing in devices and therapies for chronic diseases.
-
B.
MDT
chosen
MDT is the IATA airport code for Harrisburg International Airport, serving the Harrisburg, Pennsylvania metropolitan area.
-
C.
MDT
MDT is the state agency responsible for planning, building, and maintaining Montana’s transportation infrastructure, including highways and related systems.
-
D.
MTD
MTD is the public bus transit agency serving the Champaign–Urbana metropolitan area in Illinois.
-
E.
MTD
MTD is the primary public bus transit agency serving Santa Barbara and surrounding communities in California.
- 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0c4a7ba4881908a2747bf063d79f1 |
completed | April 16, 2026, 11:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffa13392c48190b03cbed9df5a32a6 |
completed | May 9, 2026, 9:03 p.m. |
Created at: April 10, 2026, 4:49 a.m.