Triple
T15441581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kenny |
E369914
|
entity |
| Predicate | shortFormOf |
P43
|
FINISHED |
| Object | Kenneth |
E561889
|
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: Kenneth | Statement: [Kenny, shortFormOf, Kenneth]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kenneth Context triple: [Kenny, shortFormOf, Kenneth]
-
A.
Kenneth
Kenneth is the formal given name of American country music singer, songwriter, and actor Kenny Rogers.
-
B.
Kenneth
Kenneth is the full given name of American documentary filmmaker Ken Burns, renowned for his in-depth historical films and distinctive storytelling style.
-
C.
Kenneth
chosen
Kenneth is a masculine given name of Gaelic origin, commonly used in English-speaking countries.
-
D.
Kenneth
Kenneth is a central male character in the darkly comic stage play "The Woman Who Cooked Her Husband," whose infidelity and subsequent fate drive the plot’s themes of betrayal and revenge.
-
E.
Jeffrey
Jeffrey is a masculine given name of Germanic origin, commonly used in English-speaking countries.
- 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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ef55f5c8190a32b1b6ad1daf454 |
completed | April 16, 2026, 1:44 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff21a9b9188190a3f5de3ee18c5d3e |
completed | May 9, 2026, 11:59 a.m. |
Created at: April 10, 2026, 3:21 a.m.