Triple
T2304499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Protestant Church in the Netherlands |
E51806
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | PKN |
E254297
|
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: PKN | Statement: [Protestant Church in the Netherlands, abbreviation, PKN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PKN Context triple: [Protestant Church in the Netherlands, abbreviation, PKN]
-
A.
PKN
chosen
PKN is the main Protestant denomination in the Netherlands, formed by the merger of several historic Reformed and Lutheran churches.
-
B.
KNA
KNA is the three-letter ISO 3166-1 alpha-3 country code assigned to Saint Kitts and Nevis.
-
C.
PKWN
PKWN was the Soviet-backed provisional government established in 1944 to administer liberated Polish territories during World War II and lay the groundwork for communist rule.
-
D.
PKT
PKT is the time zone used throughout Pakistan, corresponding to UTC+5 hours.
-
E.
PK
PK is the two-letter ISO 3166-1 alpha-2 country code that uniquely identifies Pakistan in international standards and systems.
- 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_69a88b0bb30c81908ded03b006d29387 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc5f2de7c819095bd74a551d8ff18 |
completed | March 7, 2026, 6:30 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae89575e648190a2e7b5b2e011bd30 |
completed | March 9, 2026, 8:48 a.m. |
Created at: March 4, 2026, 7:49 p.m.