Triple
T1370643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Open |
E30104
|
entity |
| Predicate | hasQualifyingTournament |
P12110
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Australian Open, hasQualifyingTournament, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQualifyingTournament Context triple: [Australian Open, hasQualifyingTournament, true]
-
A.
hasQualifyingRounds
chosen
Indicates that an event or competition includes preliminary qualifying rounds that participants must complete before advancing further.
-
B.
playedInTournament
Indicates that an entity participated as a competitor or player in a specific tournament.
-
C.
qualifyingCompetitionFor
Indicates that one competition serves as a qualifying event for participation in another competition.
-
D.
hasCupTieEntry
Indicates that an entity has an associated entry or participation record in a cup-style competition or knockout tournament.
-
E.
winnerQualifiedFor
Indicates that the entity identified as the winner has earned or met the conditions required to qualify for a subsequent stage, event, or status.
- 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_69a498f912008190a376a98b207b2071 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c2d7b6008190bc0303b56959ba56 |
completed | March 1, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69a4befb08b88190be966fa1aadd4bcd |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:57 p.m.