Triple
T16967833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Hood Seaplane Base |
E411587
|
entity |
| Predicate | FAAIdentifier |
P420
|
FINISHED |
| Object | LHD |
E1243254
|
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: LHD | Statement: [Lake Hood Seaplane Base, FAAIdentifier, LHD]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LHD Context triple: [Lake Hood Seaplane Base, FAAIdentifier, LHD]
-
A.
LHD
LHD is the National Rail station code for Leatherhead railway station in Surrey, England.
-
B.
LHD
chosen
LHD is the IATA airport code for Lake Hood Seaplane Base, a major seaplane facility located near Anchorage, Alaska.
-
C.
LHT
LHT is a multi-use recreational trail in the Lawrence and Hopewell areas of New Jersey, popular for walking, running, and cycling.
-
D.
LHO
LHO is the National Rail station code for Langho railway station in Lancashire, England.
-
E.
LHDIA
LHDIA is a turbulence modeling approach in fluid dynamics that approximates particle interactions by tracking their Lagrangian histories to efficiently simulate complex turbulent flows.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0a6f628819080db47285954729a |
completed | April 18, 2026, 6:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00dc09386c819088bdb2548f3fb5c8 |
completed | May 10, 2026, 7:27 p.m. |
Created at: April 10, 2026, 5:31 a.m.