Triple
T9660130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ZSSS |
E233567
|
entity |
| Predicate | isComplementaryTo |
P162
|
FINISHED |
| Object | ZSPD |
E191904
|
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: ZSPD | Statement: [ZSSS, isComplementaryTo, ZSPD]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ZSPD Context triple: [ZSSS, isComplementaryTo, ZSPD]
-
A.
ZSPD
chosen
ZSPD is the ICAO airport code for Shanghai Pudong International Airport, a major international aviation hub serving Shanghai, China.
-
B.
ZSP
ZSP is the three-letter station code used to identify St James's Park tube station on the London Underground network.
-
C.
SPZ
SPZ is the FAA airport code for Silver Springs Airport, a public-use airfield serving the Silver Springs area in Nevada, United States.
-
D.
ZP
ZP is a German vehicle registration code assigned to the Erzgebirgskreis district in the state of Saxony.
-
E.
SPS
SPS refers to the Single Payment Scheme, an agricultural subsidy system used in the European Union to provide income support to farmers through decoupled direct payments.
- 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_69ca848c1ba88190b84b410cd14627fc |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c08d0d0819086426ad6891b18db |
completed | April 1, 2026, 10:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d18a0b84a0819083191beeaf8d968b |
completed | April 4, 2026, 10 p.m. |
Created at: March 30, 2026, 8:14 p.m.