Triple
T15453125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryan Harrison |
E371699
|
entity |
| Predicate | grandSlamTitleType |
P44418
|
FINISHED |
| Object | men’s doubles |
—
|
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: men’s doubles | Statement: [Ryan Harrison, grandSlamTitleType, men’s doubles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grandSlamTitleType Context triple: [Ryan Harrison, grandSlamTitleType, men’s doubles]
-
A.
grandSlam
Indicates achieving a particularly comprehensive or dominant success, often by winning all major components or events within a defined set.
-
B.
hasWonGrandSlamTitleType
chosen
Indicates that an entity has won at least one Grand Slam title of a specified type (e.g., singles, doubles, mixed).
-
C.
GrandSlams
Indicates that an entity has won or is associated with victories in major Grand Slam tournaments within a given sport.
-
D.
grandSlamSinglesTitles
Indicates the number of Grand Slam singles tennis titles an entity has won.
-
E.
grandSlamOrder
Indicates that one event or achievement in a sequence is a grand slam and specifies its relative order or position among other such events.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f131b1481909ff099c3b844ee07 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded28276f481908c2038bb301e57cf |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:30 a.m.