Triple
T17358584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSP ČR |
E422008
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | PSP |
—
|
NE ONNED1 |
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: PSP | Statement: [PSP ČR, abbreviation, PSP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PSP Context triple: [PSP ČR, abbreviation, PSP]
-
A.
PSP
PSP is the IATA airport code for Palm Springs International Airport, which serves the Palm Springs area in Southern California.
-
B.
PSP
The PSP was a Dutch political party that combined socialist principles with a strong commitment to pacifism and anti-militarism.
-
C.
PSP
PSP refers to the President’s Surveillance Program, a post-9/11 classified U.S. intelligence initiative that authorized expanded electronic surveillance activities.
-
D.
PSP
PSP is a Pakistani political party founded by former Karachi mayor Mustafa Kamal, known for its focus on urban governance and reform.
-
E.
PSP
chosen
PSP is Poland’s nationwide professional firefighting and rescue service responsible for fire protection, emergency response, and civil safety.
- 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a4a37788190b330b7207aa424b6 |
completed | April 19, 2026, 2:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a01955e4cb481909e3193439bb85cd8 |
in_progress | May 11, 2026, 8:37 a.m. |
Created at: April 10, 2026, 5:44 a.m.