Triple
T7121734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Devdas |
E165963
|
entity |
| Predicate | characterTypeOfParvati |
P60013
|
FINISHED |
| Object | childhood sweetheart of Devdas |
—
|
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: childhood sweetheart of Devdas | Statement: [Devdas, characterTypeOfParvati, childhood sweetheart of Devdas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterTypeOfParvati Context triple: [Devdas, characterTypeOfParvati, childhood sweetheart of Devdas]
-
A.
typeOfCharacter
chosen
Indicates that one entity is a specific kind or category of character in relation to another entity.
-
B.
typeOfDeity
Indicates that one entity is classified as a specific kind or category of deity in relation to another.
-
C.
genreOfCharacter
Indicates that a character belongs to or is associated with a particular genre (such as fantasy, horror, or comedy).
-
D.
characterDescription
Indicates that one entity provides a textual description or portrayal of the characteristics, traits, or attributes of another entity.
-
E.
character2
Indicates that a second character entity is involved in the relationship or context defined by the predicate.
- 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_69c6888227bc8190a1394679e3116f90 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e61e67788190959fbd7fa6c929d3 |
completed | March 27, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c7289881909f3b533c384f9ed4 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:44 p.m.