Triple
T33626367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhea Kapoor |
E861414
|
entity |
| Predicate | stylistFor |
P120057
|
FINISHED |
| Object | Sonam Kapoor |
—
|
NE NERFINISHED |
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: Sonam Kapoor | Statement: [Rhea Kapoor, stylistFor, Sonam Kapoor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stylistFor Context triple: [Rhea Kapoor, stylistFor, Sonam Kapoor]
-
A.
stylist
chosen
Indicates that one entity serves as a stylist for another, providing professional advice or services related to appearance, fashion, or design.
-
B.
styledCelebrity
Indicates that one entity (typically a stylist or source) is responsible for selecting or creating the fashion or appearance of a celebrity.
-
C.
styleFor
Indicates a relationship where one entity defines, specifies, or is used as the style or styling configuration applied to another entity.
-
D.
inTheStyleOf
Indicates that one entity is created, performed, or presented in a manner that imitates or closely resembles the characteristic style of another entity.
-
E.
personHasNotableStyle
Indicates that a person is recognized for having a distinctive or noteworthy style.
- 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_69f34981c54c81909b33c3fa2208a52d |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f85724048190be13f0503898a67e |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:41 a.m.