Triple
T33199621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Satrangi Re |
E849862
|
entity |
| Predicate | hasRomanticDuet |
P9649
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Satrangi Re, hasRomanticDuet, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRomanticDuet Context triple: [Satrangi Re, hasRomanticDuet, yes]
-
A.
hasRomanticDuetFormat
Indicates that two entities participate together in a romantic duet format, typically as co-performers in a jointly presented romantic piece.
-
B.
hasVocalDuet
chosen
Indicates that two entities perform or participate together in a vocal duet.
-
C.
hasNotablePerformerDuo
Indicates that the subject has a notable performing duo associated with it, such as a well-known pair of artists or entertainers who perform together.
-
D.
isRomanticLeadOf
Indicates that one entity serves as the primary romantic partner or love-interest counterpart to another entity within a narrative or story.
-
E.
duetWithSpouse
Indicates that two spouses perform a duet together.
- 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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fddd373cdc8190be1b12e70e4deb1f |
completed | May 8, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69fddc6915a88190ad41e379aa3ede13 |
completed | May 8, 2026, 12:51 p.m. |
Created at: May 1, 2026, 1:29 a.m.