Triple
T25462643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Championships 1960 |
E638090
|
entity |
| Predicate | menSinglesRunnerUp |
P34926
|
FINISHED |
| Object | Neale Fraser |
—
|
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: Neale Fraser | Statement: [Australian Championships 1960, menSinglesRunnerUp, Neale Fraser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: menSinglesRunnerUp Context triple: [Australian Championships 1960, menSinglesRunnerUp, Neale Fraser]
-
A.
secondRunnerUp
Indicates that one entity finished in third place in a competition or ranking relative to the others.
-
B.
gamesWonByRunnerUp
Indicates the number of games won by the runner-up in a competition or match.
-
C.
men'sSinglesChampion
Indicates that the subject is the winner of the men's singles competition in a given event or tournament.
-
D.
notablePlayerRunnerUp
chosen
Indicates that the referenced player was a runner-up (finished in second place) in a notable competition or event.
-
E.
hasNationalRunnerUpFinishes
Indicates that an entity has achieved one or more second-place (runner-up) finishes in a national-level competition or championship.
- 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_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 2:12 p.m.