Triple
T25462648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Championships 1960 |
E638090
|
entity |
| Predicate | womenSinglesFinalScore |
P2625
|
FINISHED |
| Object | 7–5, 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: 7–5, 6–2 | Statement: [Australian Championships 1960, womenSinglesFinalScore, 7–5, 6–2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: womenSinglesFinalScore Context triple: [Australian Championships 1960, womenSinglesFinalScore, 7–5, 6–2]
-
A.
womenSinglesRunnerUp
Indicates that the person was the runner-up in a women’s singles competition or event.
-
B.
rankingPointsSinglesFinalist
Indicates the number of ranking points awarded to a player for reaching the final (but not necessarily winning) in a singles competition.
-
C.
ladiesSinglesBronzeMedalist
Indicates the relationship where an entity is the bronze medal winner in a ladies' singles competition event.
-
D.
ladiesSinglesChampion
Indicates that one entity is the winner of the women's singles competition in a given event or tournament.
-
E.
finalScore
chosen
Indicates the resulting or overall score achieved after all contributing actions, events, or evaluations are completed.
- 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.