Triple
T24902777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rebound Ace |
E623623
|
entity |
| Predicate | usedAsMainCourtSurfaceAt |
P110106
|
FINISHED |
| Object | Australian Open main show courts |
—
|
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: Australian Open main show courts | Statement: [Rebound Ace, usedAsMainCourtSurfaceAt, Australian Open main show courts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsMainCourtSurfaceAt Context triple: [Rebound Ace, usedAsMainCourtSurfaceAt, Australian Open main show courts]
-
A.
hasCourtSurface
chosen
Indicates that something (such as a court or playing area) possesses a specific type of surface.
-
B.
homeArenaSurface
Indicates the type of playing surface used in an entity’s home arena.
-
C.
hasIndoorCourts
Indicates that one entity provides or contains courts or playing areas that are located indoors.
-
D.
hasMainCourts
Indicates that an entity possesses or is associated with one or more primary courts used for official or main activities.
-
E.
servedOnCourt
Indicates that a person held an official judicial position on a particular court.
- 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_69e2fac797cc8190b30d77f4121099ac |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 18, 2026, 5:27 a.m.