Triple
T12181787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pirkkala |
E290237
|
entity |
| Predicate | airportIATAcode |
P418
|
FINISHED |
| Object | TMP |
E968310
|
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: TMP | Statement: [Pirkkala, airportIATAcode, TMP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TMP Context triple: [Pirkkala, airportIATAcode, TMP]
-
A.
TMP
chosen
TMP is the IATA airport code for Tampere–Pirkkala Airport in Tampere, Finland.
-
B.
TM
TM is the New York Stock Exchange ticker symbol for Toyota Motor Corporation, the Japanese multinational automotive manufacturer.
-
C.
.tm
.tm is the country code top-level domain (ccTLD) assigned to Turkmenistan, also popularly used worldwide for websites related to trademarks.
-
D.
TMPD
TMPD is the acronym for the Tokyo Metropolitan Police Department, the primary law enforcement agency responsible for policing Japan’s capital city and surrounding metropolitan area.
-
E.
TP
TP is the two-letter IATA airline designator used to identify TAP Air Portugal on tickets, timetables, and flight information systems.
- 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_69d6ab64de5881908d56eb7a75c6cc69 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d915fd8dac8190928059ad2b6bbbf3 |
completed | April 10, 2026, 3:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f61e505fc481909cdd2dabcef8d948 |
completed | May 2, 2026, 3:54 p.m. |
Created at: April 8, 2026, 9:50 p.m.