Triple
T25462662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Championships 1960 |
E638090
|
entity |
| Predicate | mixedDoublesRunnersUp |
P154011
|
FINISHED |
| Object | Rod Laver |
—
|
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: Rod Laver | Statement: [Australian Championships 1960, mixedDoublesRunnersUp, Rod Laver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mixedDoublesRunnersUp Context triple: [Australian Championships 1960, mixedDoublesRunnersUp, Rod Laver]
-
A.
mixedDoublesChampions
Indicates that the related entities together won a mixed doubles championship in a given event or competition.
-
B.
GrandTourDoubles
Indicates a competitive doubles tennis event or match that is part of a Grand Slam (Grand Tour) tournament series.
-
C.
hasMixedDoublesEquivalent
Indicates that one entity corresponds to or serves as the mixed doubles counterpart or equivalent of another entity.
-
D.
homeTeamRunnerUp
Indicates that the referenced team finished in second place (runner-up) in a competition held at its home venue or location.
-
E.
finishedRunnersUpIn
chosen
Indicates that one entity concluded a competition or contest in the runners-up position relative to another entity or event.
- 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f72d0cc08190ba91a9dc39b1d848 |
completed | May 2, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 2:12 p.m.