Triple
T6215231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stadler FLIRT |
E138968
|
entity |
| Predicate | operator |
P179
|
FINISHED |
| Object | PKP |
E479810
|
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: PKP | Statement: [Stadler FLIRT, operator, PKP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PKP Context triple: [Stadler FLIRT, operator, PKP]
-
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.
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.
-
C.
PK
PK is the two-letter ISO 3166-1 alpha-2 country code that uniquely identifies Pakistan in international standards and systems.
-
D.
PK
PK is a compact bitmap font file format traditionally used by TeX systems to store rasterized glyphs generated from METAFONT sources.
-
E.
PKN
PKN is the main Protestant denomination in the Netherlands, formed by the merger of several historic Reformed and Lutheran churches.
- 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_69c008ada364819096c9e92c74d639b5 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062a0e0488190b71b42386bacf982 |
completed | March 22, 2026, 9:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c20dacf1788190a655c39bd248fde8 |
completed | March 24, 2026, 4:06 a.m. |
Created at: March 22, 2026, 4:21 p.m.