Triple
T7438006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gorlice County |
E171668
|
entity |
| Predicate | vehicleRegistrationCode |
P1173
|
FINISHED |
| Object | KGR |
E135716
|
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: KGR | Statement: [Gorlice County, vehicleRegistrationCode, KGR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KGR Context triple: [Gorlice County, vehicleRegistrationCode, KGR]
-
A.
KGR
chosen
KGR is the Polish vehicle registration code assigned to the Gorlice area in the Lesser Poland Voivodeship.
-
B.
KGRB
KGRB is the ICAO airport code for Austin Straubel International Airport serving the Green Bay, Wisconsin area.
-
C.
KGN
KGN is the standard three-letter abbreviation used for the Kingston Frontenacs, a major junior ice hockey team in the Ontario Hockey League.
-
D.
KBGR
KBGR is the ICAO airport code for Bangor International Airport, a public airport serving Bangor, Maine, in the United States.
-
E.
KGG
KGG is the abbreviated name of Kings Guard Gaming, an NBA 2K League esports team affiliated with the Sacramento Kings.
- 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_69c68a64228c8190affaec2a8127ce7b |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f34aa3388190ac300cf934042d78 |
completed | March 27, 2026, 9:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8278cd9cc8190b88767c1432b3007 |
completed | March 28, 2026, 7:10 p.m. |
Created at: March 27, 2026, 3:13 p.m.