Triple
T21267744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Studio 54 |
E524172
|
entity |
| Predicate | convertedToTheatre |
P115334
|
FINISHED |
| Object | late 1990s |
—
|
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: late 1990s | Statement: [Studio 54, convertedToTheatre, late 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convertedToTheatre Context triple: [Studio 54, convertedToTheatre, late 1990s]
-
A.
transferredToTheatre
chosen
Indicates that an entity has been moved or reassigned from its previous location or status into a theatre (such as an operating theatre or performance venue).
-
B.
appliedToTheater
Indicates that an application, request, or action has been directed toward or submitted to a specific theater.
-
C.
intendedTheatre
Indicates a relationship where an entity is planned, designed, or meant to be performed, shown, or take place in a particular theatre.
-
D.
implementedInTheatre
Indicates that an event, work, or action is carried out, performed, or realized within a theatre setting.
-
E.
usedTheatreFrom
Indicates that one entity made use of or operated within a particular theatre (such as a theater building, venue, or performance space) during some period or context.
- 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_69e0b5156d7881909bd4f83676590715 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735ee38cc81909b4e7c5996bb64f9 |
completed | April 21, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69e5f6161dac8190b06009cd180e3ff7 |
completed | April 20, 2026, 9:47 a.m. |
Created at: April 16, 2026, 4 p.m.