Triple
T3161545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beijing Capital International Airport |
E66112
|
entity |
| Predicate | IATACode |
P418
|
FINISHED |
| Object | PEK |
E66112
|
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: PEK | Statement: [Beijing Capital International Airport, IATACode, PEK]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PEK Context triple: [Beijing Capital International Airport, IATACode, PEK]
-
A.
PEK
chosen
PEK is the IATA airport code for Beijing Capital International Airport, one of the busiest and largest aviation hubs in China and the world.
-
B.
Pekar
Pekar is a surname of Central or Eastern European origin, notably associated with several cultural and artistic figures.
-
C.
Pekat
Pekat is a settlement on the Indonesian island of Sumbawa that was devastated by the catastrophic 1815 eruption of Mount Tambora.
-
D.
Nieuwe Pekela
Nieuwe Pekela is a village in the municipality of Pekela in the province of Groningen in the northeastern Netherlands.
-
E.
Pe
Pe is a Hebrew consonant letter that represents a "p" or "f" sound and has both standard and final written forms.
- 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_69ad85850c1481908a9e9c6242238de2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada617824c8190a293230041b2f1ea |
completed | March 8, 2026, 4:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b2250fa3348190b1dc2825147a2fde |
completed | March 12, 2026, 2:29 a.m. |
Created at: March 8, 2026, 3:06 p.m.