Triple
T8499742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richmond Hill Centre for the Performing Arts |
E201184
|
entity |
| Predicate | hasRehearsalSpace |
P28086
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Richmond Hill Centre for the Performing Arts, hasRehearsalSpace, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRehearsalSpace Context triple: [Richmond Hill Centre for the Performing Arts, hasRehearsalSpace, yes]
-
A.
hasRehearsalSpaces
chosen
Indicates that an entity provides or contains designated spaces specifically intended for rehearsing activities or performances.
-
B.
hasImprovisation
Indicates that an entity includes, involves, or is characterized by improvisational elements or unscripted creative actions in relation to another entity or context.
-
C.
hasReprise
Indicates that an action, theme, or element is repeated or returns after its initial occurrence.
-
D.
hasDanceFloor
Indicates that a place or venue includes a designated area intended for dancing.
-
E.
hasRecitalsCount
Indicates the number of recitals associated with a given entity.
- 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_69ca831fe47c8190b5c57b456d2aefa0 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe5984d7481908c41c57bef9cf254 |
completed | March 31, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:14 p.m.