Triple
T26768817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guelph River Run Centre |
E675021
|
entity |
| Predicate | seatingCapacityMainStage |
P2491
|
FINISHED |
| Object | 785 |
—
|
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: 785 | Statement: [Guelph River Run Centre, seatingCapacityMainStage, 785]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seatingCapacityMainStage Context triple: [Guelph River Run Centre, seatingCapacityMainStage, 785]
-
A.
isMainStageOf
Indicates that one entity serves as the primary or central stage or platform on which the other entity occurs, is presented, or is featured.
-
B.
mainHallCapacity
Indicates the maximum number of people that the main hall can accommodate at one time.
-
C.
seatingCapacity
chosen
Indicates the maximum number of people that something (typically a venue or vehicle) is designed or allowed to seat.
-
D.
audienceCapacityType
Indicates the classification or type of capacity used to describe how many audience members a venue or event space can accommodate.
-
E.
standingCapacity
Indicates the maximum number of people that are allowed or able to stand in a given space or vehicle.
- 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_69eecda85298819097ee1c38a3d772e7 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6192af84481908f00b324e81db779 |
completed | May 2, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 4:01 a.m.