Triple
T5544027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keren Kayemet LeYisrael |
E145362
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | KKL |
E145363
|
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: KKL | Statement: [Keren Kayemet LeYisrael, hasAbbreviation, KKL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KKL Context triple: [Keren Kayemet LeYisrael, hasAbbreviation, KKL]
-
A.
KKL
chosen
KKL is the Hebrew acronym for Keren Kayemeth LeIsrael, the Jewish National Fund organization known for land development, afforestation, and environmental projects in Israel.
-
B.
KLE
KLE is the vehicle registration code for the district of Cleves (Kleve) in the German state of North Rhine-Westphalia.
-
C.
KKH
KKH is the abbreviation for the Karakoram Highway, a major high-altitude road linking Pakistan and China through the Karakoram mountain range.
-
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_69c008fa64888190adae56c8f9ea4031 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01fcad7d88190b83bb4ecb3b34bfd |
completed | March 22, 2026, 4:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c02822fb80819087474c37d6dc4d2b |
completed | March 22, 2026, 5:34 p.m. |
Created at: March 22, 2026, 3:35 p.m.