Triple
T24489601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sara Errani |
E617604
|
entity |
| Predicate | notableDoublesPartner |
P44416
|
FINISHED |
| Object | Roberta Vinci |
—
|
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: Roberta Vinci | Statement: [Sara Errani, notableDoublesPartner, Roberta Vinci]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDoublesPartner Context triple: [Sara Errani, notableDoublesPartner, Roberta Vinci]
-
A.
hasDoublesPartner
chosen
Indicates that one entity serves as the doubles partner of another in a paired or team-based activity or sport.
-
B.
pairedInDoubleBillWith
Indicates that two performances, films, or shows are scheduled or presented together as a combined double-feature program.
-
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.
notableDuo
Indicates that two entities are widely recognized together as a famous or significant pair.
-
E.
notableCouple
Indicates that two entities are widely recognized or documented as a couple in a notable or significant relationship.
- 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_69e2d7f4e6bc8190aec540ae3b9ed7f2 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:22 a.m.