Triple
T12016549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shreveport Regional Airport |
E286039
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | SHV |
E960741
|
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: SHV | Statement: [Shreveport Regional Airport, FAAcode, SHV]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SHV Context triple: [Shreveport Regional Airport, FAAcode, SHV]
-
A.
SHV
chosen
SHV is the three-letter IATA airport code for Shreveport Regional Airport in Shreveport, Louisiana.
-
B.
SVH
SVH is the FAA location identifier for Statesville Regional Airport, a public airport serving the Statesville area in North Carolina.
-
C.
SVH
SVH is the FAA location identifier for Stanly County Airport, a public-use airport serving Stanly County, North Carolina.
-
D.
SHVO
SHVO is a New York–based real estate investment and development firm known for acquiring and redeveloping high-profile luxury and landmark properties.
-
E.
SHW
SHW is the IATA airport code for Sharurah Domestic Airport in Sharurah, Saudi Arabia.
- 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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903d9b17881908894be80d7c1b64e |
completed | April 10, 2026, 2:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f49d4156ec8190bfc6d1180ac41d06 |
completed | May 1, 2026, 12:32 p.m. |
Created at: April 8, 2026, 9:47 p.m.