Triple
T19278636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tony Award for Best Lighting Design |
E482123
|
entity |
| Predicate | separatedIntoPlayAndMusical |
P12217
|
FINISHED |
| Object | 2005 |
—
|
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: 2005 | Statement: [Tony Award for Best Lighting Design, separatedIntoPlayAndMusical, 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: separatedIntoPlayAndMusical Context triple: [Tony Award for Best Lighting Design, separatedIntoPlayAndMusical, 2005]
-
A.
partOfMusical
Indicates that something is a component, segment, or element belonging to a larger musical work or performance.
-
B.
separatedInto
chosen
Indicates that something has been divided or split into distinct parts, groups, or components.
-
C.
separatedIn
Indicates that two or more entities, once together or associated, have been divided, split, or otherwise placed into distinct parts, groups, or locations.
-
D.
hasMusicalArrangementCharacteristic
Indicates that a musical arrangement possesses a specific characteristic, feature, or quality.
-
E.
hasMusicalForm
Indicates that one entity (typically a musical work or piece) is characterized by or structured according to a particular musical form.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbbe6e9c8190a7fa2ef3aa598e6c |
completed | April 20, 2026, 10:11 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:30 p.m.