Triple
T14380511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terminal 3E |
E356587
|
entity |
| Predicate | IATAAirportCodeOfServedAirport |
P2569
|
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: [Terminal 3E, IATAAirportCodeOfServedAirport, PEK]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PEK Context triple: [Terminal 3E, IATAAirportCodeOfServedAirport, 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.
Peket
Peket is a traditional juniper-flavored spirit from the Liège region of Belgium, often enjoyed as a local specialty at festivals and bars.
-
D.
Pekat
Pekat is a settlement on the Indonesian island of Sumbawa that was devastated by the catastrophic 1815 eruption of Mount Tambora.
-
E.
Peketa
Peketa is a small coastal settlement in New Zealand’s South Island, located just south of the town of Kaikōura.
- 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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de900bbfb08190a1e56f281a2374c0 |
completed | April 14, 2026, 7:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd4c590660819090652e75418f2747 |
completed | May 8, 2026, 2:37 a.m. |
Created at: April 10, 2026, 1:16 a.m.