Triple
T3320308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kevin Durant |
E69778
|
entity |
| Predicate | nickname |
P55
|
FINISHED |
| Object | KD |
E69778
|
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: KD | Statement: [Kevin Durant, nickname, KD]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KD Context triple: [Kevin Durant, nickname, KD]
-
A.
KD
chosen
KD is the widely used nickname of Kevin Durant, an elite NBA scorer and multi-time champion regarded as one of the greatest basketball players of his generation.
-
B.
KD
KD is the official vehicle registration code used to identify motor vehicles registered in Kaduna State, Nigeria.
-
C.
DK
DK is the ISO 3166-1 alpha-2 country code for Denmark, a Nordic nation in Northern Europe.
-
D.
DK
DK is a British illustrated reference publisher best known for its highly visual nonfiction books for children and adults across topics like science, history, travel, and nature.
-
E.
KC
KC is a common shorthand nickname for Kansas City, Missouri, a major Midwestern U.S. city known for its jazz heritage, barbecue, and sports teams.
- 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_69ad85a0bb048190a5458d2738012d61 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb13a4e948190841134d6ae6ef432 |
completed | March 8, 2026, 5:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b31a776f3881908e8b198f31921453 |
completed | March 12, 2026, 7:56 p.m. |
Created at: March 8, 2026, 3:11 p.m.