Triple
T25462653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Championships 1960 |
E638090
|
entity |
| Predicate | menDoublesFinalScore |
P159760
|
FINISHED |
| Object | 6–2, 3–6, 13–11, 4–6, 6–3 |
—
|
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: 6–2, 3–6, 13–11, 4–6, 6–3 | Statement: [Australian Championships 1960, menDoublesFinalScore, 6–2, 3–6, 13–11, 4–6, 6–3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: menDoublesFinalScore Context triple: [Australian Championships 1960, menDoublesFinalScore, 6–2, 3–6, 13–11, 4–6, 6–3]
-
A.
menDoublesRunnersUp
Indicates that the referenced entities were the runners-up in the men's doubles event of a competition or tournament.
-
B.
mixedDoublesChampions
Indicates that the related entities together won a mixed doubles championship in a given event or competition.
-
C.
opponentFinalScore
Indicates the final score achieved by an opposing participant or team in a contest or game.
-
D.
doubleWinner
Indicates that the same entity has won the relevant award, contest, or recognition twice.
-
E.
men'sSinglesChampion
Indicates that the subject is the winner of the men's singles competition in a given event or tournament.
- F. None of above. chosen
Provenance (4 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_69f5f7a205688190b8f36bff5013247c |
completed | May 2, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 21, 2026, 2:12 p.m.