Triple
T3895658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WACA Ground |
E88163
|
entity |
| Predicate | formerPrimaryTestVenueFor |
P13839
|
FINISHED |
| Object | Perth international matches |
—
|
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: Perth international matches | Statement: [WACA Ground, formerPrimaryTestVenueFor, Perth international matches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerPrimaryTestVenueFor Context triple: [WACA Ground, formerPrimaryTestVenueFor, Perth international matches]
-
A.
previousVenue
chosen
Indicates that one venue was used or occupied before another in a sequence of venues.
-
B.
primaryVenueFor
Indicates that one entity serves as the main or principal venue or location for events, activities, or operations associated with another entity.
-
C.
replacedVenue
Indicates that one venue has taken the place of another as its successor location or site.
-
D.
conferenceOfPrimaryTenant
Indicates that a conference or meeting is associated with, organized by, or held for the primary tenant.
-
E.
testDebutVenue
Indicates the venue or location where an entity (such as a person, product, or performance) made its first test appearance or trial debut.
- 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_69aed9466d548190939f5217a23ed4ac |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1abe2dc81909c18aeae9b286898 |
completed | March 9, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69aee75b5b808190a348a31b1325d3d0 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:21 p.m.