Triple
T8505174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cain’s Ballroom |
E201315
|
entity |
| Predicate | convertedToBallroom |
P82868
|
FINISHED |
| Object | 1930s |
—
|
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: 1930s | Statement: [Cain’s Ballroom, convertedToBallroom, 1930s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convertedToBallroom Context triple: [Cain’s Ballroom, convertedToBallroom, 1930s]
-
A.
ballroomSpace
Indicates that one entity provides or constitutes a ballroom area or venue space for events or activities.
-
B.
hasBallrooms
Indicates that an entity possesses or contains one or more ballrooms as part of its facilities or structure.
-
C.
balletType
Indicates that one entity is classified as a specific type or category of ballet in relation to another entity.
-
D.
hasBalletMaster
Indicates that an entity is associated with or overseen by a specific ballet master responsible for its ballet-related training, direction, or instruction.
-
E.
choreographedIn
Indicates that an entity (typically a choreographer or group) created or arranged the choreography for a performance, work, or event in a specified context or production.
- F. None of above. chosen
Provenance (4 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_69cbe5d8b7208190b199c56bf366c692 |
completed | March 31, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69cbd10cfd208190a519049fad32c508 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe12dd0b88190a38ec4d15dcc870b |
completed | March 31, 2026, 2:58 p.m. |
Created at: March 30, 2026, 6:14 p.m.