Triple
T21330916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krittika |
E525894
|
entity |
| Predicate | associatedWithTemperament |
P32341
|
FINISHED |
| Object | rakshasa gana |
—
|
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: rakshasa gana | Statement: [Krittika, associatedWithTemperament, rakshasa gana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithTemperament Context triple: [Krittika, associatedWithTemperament, rakshasa gana]
-
A.
hasTemperament
chosen
Indicates that an entity possesses a particular characteristic style of behavior, mood, or emotional disposition.
-
B.
associatedAnimalBreed
Indicates that there is a relationship linking an entity to a specific breed of animal with which it is connected or identified.
-
C.
roleInBreed
Indicates that an entity has a specific functional or social role within the context of a particular breed.
-
D.
associatedWithAnimal
Indicates a relationship where an entity has a connection, link, or relevance to an animal.
-
E.
associatedCharacterTrait
Indicates a relationship where a character is linked to, or described by, a particular trait or quality.
- 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_69e0b51b90788190a4dd823d962626da |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7ab530a1c81909bb37c2a3407d9e6 |
completed | April 21, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:42 p.m.