Triple
T11814588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICC Sydney |
E280964
|
entity |
| Predicate | hasBallroomCapacity |
P96470
|
FINISHED |
| Object | 2000 guests |
—
|
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: 2000 guests | Statement: [ICC Sydney, hasBallroomCapacity, 2000 guests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBallroomCapacity Context triple: [ICC Sydney, hasBallroomCapacity, 2000 guests]
-
A.
hasBallrooms
Indicates that an entity possesses or contains one or more ballrooms as part of its facilities or structure.
-
B.
standingCapacity
Indicates the maximum number of people that are allowed or able to stand in a given space or vehicle.
-
C.
roomCapacity
chosen
Indicates the maximum number of people or occupants that a room is designed or allowed to hold.
-
D.
concertCapacity
Indicates the maximum number of people that can be accommodated at a concert event or venue.
-
E.
audienceCapacityType
Indicates the classification or type of capacity used to describe how many audience members a venue or event space 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a658f918819092c2db05fe2ab0ce |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a24e9a088190aff7932d1ff93dbf |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.