Triple
T25220501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Open (tennis) venues |
E631947
|
entity |
| Predicate | hostsNightSessions |
P158426
|
FINISHED |
| Object | Margaret Court Arena |
—
|
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: Margaret Court Arena | Statement: [Australian Open (tennis) venues, hostsNightSessions, Margaret Court Arena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostsNightSessions Context triple: [Australian Open (tennis) venues, hostsNightSessions, Margaret Court Arena]
-
A.
hostsEvent
Indicates that an entity organizes and provides the venue or setting for an event to take place.
-
B.
seatingCapacityNightSessions
Indicates the number of people that can be seated during night-time sessions or events.
-
C.
heldSessionsIn
Indicates that an entity organized or conducted one or more sessions, meetings, or events at a specified location or venue.
-
D.
hostedDuring
Indicates that one entity hosted, organized, or held another entity (such as an event or activity) within a specified time period.
-
E.
hostedShow
Indicates that one entity served as the host or presenter of a particular show or program involving the other entity.
- F. None of above. chosen
Provenance (4 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_69e75a8e0f688190a7aebe9a4815e25b |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f47cbe66648190a46a29d187ab2c47 |
completed | May 1, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 1:03 p.m.