Triple
T30679097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Singin’ in the Rain (stage choreography) |
E781002
|
entity |
| Predicate | hasIntendedVenue |
P55397
|
FINISHED |
| Object | proscenium theatre |
—
|
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: proscenium theatre | Statement: [Singin’ in the Rain (stage choreography), hasIntendedVenue, proscenium theatre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIntendedVenue Context triple: [Singin’ in the Rain (stage choreography), hasIntendedVenue, proscenium theatre]
-
A.
hasPrincipalVenue
Indicates that an entity has a primary or main venue where its activities, events, or operations predominantly take place.
-
B.
hasAttachedVenue
Indicates that one entity has another entity linked or associated with it as a venue.
-
C.
hasVenueContext
chosen
Indicates that an entity is associated with a particular venue or setting that provides contextual information about where it occurs or is situated.
-
D.
hasQualifyingVenue
Indicates that an entity is associated with a venue that meets specified qualifying criteria or standards.
-
E.
locatedInOperatedVenue
Indicates that an entity is situated within a venue that is managed or operated by a specified agent or organization.
- 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_69f224a7fc208190a07d6d3879b31640 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff069ec1348190815375c5c9e38404 |
completed | May 9, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69ff05ba57f88190a45d20f18044e0fb |
completed | May 9, 2026, 10 a.m. |
Created at: April 29, 2026, 8:32 p.m.