Triple
T21983300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State National Council of Poland |
E542893
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | KRN |
—
|
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: KRN | Statement: [State National Council of Poland, abbreviation, KRN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KRN Context triple: [State National Council of Poland, abbreviation, KRN]
-
A.
KRN
chosen
KRN is the abbreviation for the Krajowa Rada Narodowa, the wartime Polish parliament established by communists in 1943 as a rival authority to the government-in-exile.
-
B.
KRNAP
KRNAP is the Czech abbreviation for Krkonoše National Park, a protected mountain area in the Krkonoše range known for its unique alpine ecosystems and popular outdoor recreation.
-
C.
KRNO
KRNO is the ICAO airport code for Reno–Tahoe International Airport in Reno, Nevada, a major commercial and general aviation facility serving the Reno–Tahoe region.
-
D.
RKR
RKR is the vehicle registration code assigned to vehicles registered in the Rymanów area of Poland.
-
E.
KRP
KRP is the IATA airport code for Karup Airport, a regional airport in Denmark.
- 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_69e0c48136b081908831fa907cc02e18 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1270629588190aea32fbe630e4cba |
completed | April 28, 2026, 9:30 p.m. |
Created at: April 16, 2026, 8:04 p.m.