Triple
T5838219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bergkrystallen |
E129526
|
entity |
| Predicate | hasStationCode |
P1289
|
FINISHED |
| Object | BKR |
E275177
|
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: BKR | Statement: [Bergkrystallen, hasStationCode, BKR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BKR Context triple: [Bergkrystallen, hasStationCode, BKR]
-
A.
BKR
chosen
BKR is the postal code prefix used for addresses in the town of Birkirkara in Malta.
-
B.
BKR
BKR was the abbreviated name of the People's Security Agency, an early post-World War II Indonesian security and defense organization.
-
C.
BK
BK is a common abbreviation for Brooklyn, a borough of New York City known for its cultural diversity, arts scene, and historic neighborhoods.
-
D.
BKL
BKL is an alternative name for the Big Circle Line, a major circular metro line in Moscow’s rapid transit system.
-
E.
BKL
BKL is the FAA airport code for Burke Lakefront Airport, a public airport located on the shore of Lake Erie in Cleveland, Ohio.
- 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_69c0084af79c81908af128ccc29983d0 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c034a66c448190a6ea7f9827cbffe9 |
completed | March 22, 2026, 6:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0a19a6554819086cdae499f4d2247 |
completed | March 23, 2026, 2:12 a.m. |
Created at: March 22, 2026, 3:54 p.m.