Triple
T34486873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | If a Man Answers |
E885352
|
entity |
| Predicate | starCouple |
P35186
|
FINISHED |
| Object | Sandra Dee and Bobby Darin |
—
|
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: Sandra Dee and Bobby Darin | Statement: [If a Man Answers, starCouple, Sandra Dee and Bobby Darin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: starCouple Context triple: [If a Man Answers, starCouple, Sandra Dee and Bobby Darin]
-
A.
notableCouple
chosen
Indicates that two entities are widely recognized or documented as a couple in a notable or significant relationship.
-
B.
isRomanticLeadOf
Indicates that one entity serves as the primary romantic partner or love-interest counterpart to another entity within a narrative or story.
-
C.
starsReunited
Indicates that previously separated or former co-stars have come together again, such as reappearing or collaborating in a shared context.
-
D.
starredActor
Indicates that an actor performed a leading or significant role in a particular production or work.
-
E.
starredActorWith
Indicates that one entity participated as an actor in a production together with another specified actor.
- 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_69f349c947fc81909d30b53c194d6ea1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71fb1ab3881908e2f7c0e6f23db49 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:01 a.m.