Triple
T7121735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Devdas |
E165963
|
entity |
| Predicate | characterTypeOfChandramukhi |
P60013
|
FINISHED |
| Object | courtesan who loves 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: courtesan who loves Devdas | Statement: [Devdas, characterTypeOfChandramukhi, courtesan who loves Devdas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterTypeOfChandramukhi Context triple: [Devdas, characterTypeOfChandramukhi, courtesan who loves Devdas]
-
A.
typeOfCharacter
chosen
Indicates that one entity is a specific kind or category of character in relation to another entity.
-
B.
characterIn
Indicates that an entity appears as a character within a specified work, story, or narrative.
-
C.
character2
Indicates that a second character entity is involved in the relationship or context defined by the predicate.
-
D.
character1
Indicates that the subject is identified as the first or primary character in a narrative or context.
-
E.
character3
Indicates a tertiary or additional character role associated with an entity, typically the third distinct character linked within a given context or work.
- 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.