Triple
T16603872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cairns Convention Centre |
E403400
|
entity |
| Predicate | basketballCapacity |
P103582
|
FINISHED |
| Object | 5300 |
—
|
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: 5300 | Statement: [Cairns Convention Centre, basketballCapacity, 5300]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basketballCapacity Context triple: [Cairns Convention Centre, basketballCapacity, 5300]
-
A.
capacityForBasketball
Indicates the ability or suitability of an entity to play or perform well in basketball.
-
B.
homeArenaCapacity
Indicates the maximum number of spectators that can be accommodated in an entity’s home arena.
-
C.
venueCapacityApproximate
chosen
Indicates an approximate or estimated capacity of a venue in terms of how many people it can accommodate.
-
D.
homeBasketballArena
Indicates that a specified basketball arena serves as the home venue for a particular team or organization.
-
E.
replacedAsPrimaryBasketballVenueBy
Indicates that one basketball venue ceased to be the main or primary location for games or events and was succeeded in that role by another venue.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35d77d97c8190a63330897e49a9c9 |
completed | April 18, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69e296aabc508190b3836a91b49113ad |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.