Triple
T16569260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kasha |
E402540
|
entity |
| Predicate | usedAsNickname |
P114088
|
FINISHED |
| Object | true |
—
|
LITERAL 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: true | Statement: [Kasha, usedAsNickname, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsNickname Context triple: [Kasha, usedAsNickname, true]
-
A.
usedAsNicknameSince
Indicates that one entity has been used as a nickname for another entity starting from a specified point in time.
-
B.
usesNicknameOf
Indicates that one entity refers to another entity by a nickname derived from or associated with that other entity’s name.
-
C.
usedPseudonym
Indicates that an entity performed an action or participated in a context under a name that was not their real or primary identity.
-
D.
usedNicknameSystem
chosen
Indicates that one entity referred to another entity using a nickname rather than their formal name.
-
E.
usedAsSurname
Indicates that something functions as a family name borne by a person or group of people.
- 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35773c00c819091731bebc02a69bb |
completed | April 18, 2026, 10:05 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:16 a.m.