Triple
T16029840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KPSC |
E388814
|
entity |
| Predicate | hasIATACode |
P2569
|
FINISHED |
| Object | PSC |
E124743
|
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: PSC | Statement: [KPSC, hasIATACode, PSC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PSC Context triple: [KPSC, hasIATACode, PSC]
-
A.
PSC
chosen
PSC is the IATA airport code for Tri-Cities Airport serving Pasco and the surrounding Tri-Cities region in Washington State, USA.
-
B.
PSC
PSC is the abbreviation for the European Union’s Political and Security Committee, a key body responsible for shaping the EU’s foreign and security policy.
-
C.
PSC
PSC is the commonly used abbreviation for Public Safety Canada, the federal department responsible for national security and emergency management.
-
D.
PSC
PSC is the commonly used abbreviation for Pensacola State College, a public institution of higher education located in Pensacola, Florida.
-
E.
PSC
PSC is the National Rail station code for Prescot railway station in Merseyside, England.
- 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1832a56ec8190a47fd2cf83a42fd4 |
completed | April 17, 2026, 12:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffcf35ae808190aeb154a273c32a70 |
completed | May 10, 2026, 12:20 a.m. |
Created at: April 10, 2026, 4:56 a.m.