Triple
T19960955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PKP Intercity |
E479810
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | PKP IC |
—
|
NE NERFINISHED |
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: PKP IC | Statement: [PKP Intercity, abbreviation, PKP IC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PKP IC Context triple: [PKP Intercity, abbreviation, PKP IC]
-
A.
PKP IC
chosen
PKP IC is the commonly used abbreviation for PKP Intercity, Poland’s primary operator of long-distance passenger rail services.
-
B.
PKP
PKP is Poland’s state-owned national railway operator, responsible for much of the country’s passenger and freight rail transport infrastructure.
-
C.
PKKP
PKKP is the abbreviation for Polska Krajowa Kasa Pożyczkowa, a historical Polish national loan office that played a key role in the country’s early financial and monetary system.
-
D.
PKS
PKS is the station code for Park Street, a major metro station in Kolkata, India.
-
E.
PKS
PKS is the standard radio source designation prefix used for astronomical objects cataloged from observations with the Parkes Observatory in Australia.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65af4520c81909986a47289ba801e |
completed | April 20, 2026, 4:57 p.m. |
Created at: April 10, 2026, 1:54 p.m.