Triple
T8616255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leonard Bosack |
E204044
|
entity |
| Predicate | coFounded |
P104
|
FINISHED |
| Object | XKL LLC |
E204046
|
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: XKL LLC | Statement: [Leonard Bosack, coFounded, XKL LLC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: XKL LLC Context triple: [Leonard Bosack, coFounded, XKL LLC]
-
A.
XKL LLC
chosen
XKL LLC is a technology company specializing in high-performance optical networking and data communication solutions.
-
B.
ZKL
ZKL is the vehicle registration code assigned to cars registered in Kołobrzeg, a city in northwestern Poland.
-
C.
KLA
KLA is an ethnic Albanian paramilitary organization that fought for Kosovo’s independence from Serbia in the late 1990s.
-
D.
KLA
KLA is the commonly used abbreviation for the Karnataka Legislative Assembly, the lower house of the state legislature in Karnataka, India.
-
E.
HXL
HXL (Humanitarian Exchange Language) is a lightweight data standard designed to improve the interoperability, quality, and rapid sharing of humanitarian data across organizations and crises.
- 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_69ca832ceab8819096e4a9f546695079 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc4703b57c81909511de72fa5c38d7 |
completed | March 31, 2026, 10:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cea923ae148190a973ef8ad6ccac9a |
completed | April 2, 2026, 5:36 p.m. |
Created at: March 30, 2026, 6:25 p.m.