Triple
T5782066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | THF |
E128181
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | THF |
E128181
|
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: THF | Statement: [THF, IATAcode, THF]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: THF Context triple: [THF, IATAcode, THF]
-
A.
THF
chosen
THF is the former Berlin Tempelhof Airport, a historically significant airfield known for its role in the Berlin Airlift and its later conversion into a vast urban park.
-
B.
HTF
HTF is a common abbreviation for Housing Trust Fund programs that provide dedicated public funding to support affordable housing development and preservation.
-
C.
HVF
HVF is a data-focused startup and innovation lab created by entrepreneur Max Levchin to explore and build companies around large-scale data problems.
-
D.
HEF
HEF is the FAA location identifier for Manassas Regional Airport in Virginia, a public airport serving general aviation and regional air traffic.
-
E.
TH
TH is the two-letter ISO 3166-1 alpha-2 country code assigned to Thailand for international standardization and identification.
- 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_69c0084450048190bc647b649a05136b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02a17315881908aa12a830ba5f22b |
completed | March 22, 2026, 5:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c07e7773888190bd8c3e1d7df62f5c |
completed | March 22, 2026, 11:42 p.m. |
Created at: March 22, 2026, 3:50 p.m.