Triple
T25462663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Championships 1960 |
E638090
|
entity |
| Predicate | mixedDoublesFinalScore |
P2625
|
FINISHED |
| Object | 1–6, 9–7, 6–2 |
—
|
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: 1–6, 9–7, 6–2 | Statement: [Australian Championships 1960, mixedDoublesFinalScore, 1–6, 9–7, 6–2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mixedDoublesFinalScore Context triple: [Australian Championships 1960, mixedDoublesFinalScore, 1–6, 9–7, 6–2]
-
A.
mixedDoublesChampions
Indicates that the related entities together won a mixed doubles championship in a given event or competition.
-
B.
opponentFinalScore
Indicates the final score achieved by an opposing participant or team in a contest or game.
-
C.
finalOfficialMatchScore
Indicates the conclusive, authoritative score assigned to a match after all reviews, adjustments, or validations are completed.
-
D.
finalScore
chosen
Indicates the resulting or overall score achieved after all contributing actions, events, or evaluations are completed.
-
E.
finalReplayScore
Indicates the score or result achieved at the end of a replayed event, game, or scenario.
- 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_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 2:12 p.m.