Triple
T16338923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perth Scorchers |
E396744
|
entity |
| Predicate | previousHomeGroundCapacity |
P64680
|
FINISHED |
| Object | WACA Ground about 20,000 |
—
|
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: WACA Ground about 20,000 | Statement: [Perth Scorchers, previousHomeGroundCapacity, WACA Ground about 20,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousHomeGroundCapacity Context triple: [Perth Scorchers, previousHomeGroundCapacity, WACA Ground about 20,000]
-
A.
homeStadiumCapacity
Indicates the seating capacity of the stadium that serves as a team's or organization's home venue.
-
B.
previousHomeGroundLocatedIn
Indicates that the location specified is where an entity’s former or earlier home ground was situated.
-
C.
homeArenaCapacity
Indicates the maximum number of spectators that can be accommodated in an entity’s home arena.
-
D.
formerStadiumCapacityApprox
chosen
Indicates that an entity’s past stadium capacity is approximately equal to the given number, rather than an exact figure.
-
E.
stadiumCapacityApprox
Indicates an approximate number of people that a stadium can accommodate.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2da08fbc88190a31127d10ca633d6 |
completed | April 18, 2026, 1:10 a.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.