Triple
T29558239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ajith Kumar |
E749963
|
entity |
| Predicate | gainedNicknameFrom |
P44320
|
FINISHED |
| Object | Dheena |
—
|
NE NERFINISHED |
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: Dheena | Statement: [Ajith Kumar, gainedNicknameFrom, Dheena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gainedNicknameFrom Context triple: [Ajith Kumar, gainedNicknameFrom, Dheena]
-
A.
changedNicknameTo
Indicates that an entity has altered another entity’s nickname to a specified new nickname.
-
B.
nickNameGivenBy
chosen
Indicates that one entity assigns or uses a particular nickname for another entity.
-
C.
usedAsNicknameSince
Indicates that one entity has been used as a nickname for another entity starting from a specified point in time.
-
D.
dedicatedToOrNicknameOf
Indicates that one entity is either the dedicatee of something (e.g., a work, object, or honor) or serves as an alternative name or nickname for another entity.
-
E.
hasAffectionateNicknameFor
Indicates that one entity uses or assigns a fond, affectionate, or endearing nickname to another entity.
- F. None of above.
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_69f0bd4919e48190942b2a13d5b97d03 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66d1b59e481908e7a4676160788c0 |
completed | May 2, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 5:18 p.m.