Triple
T38389720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Without You |
E899679
|
entity |
| Predicate | intendedPerformanceSetting |
P71221
|
FINISHED |
| Object | stage musical |
—
|
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: stage musical | Statement: [Without You, intendedPerformanceSetting, stage musical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedPerformanceSetting Context triple: [Without You, intendedPerformanceSetting, stage musical]
-
A.
intendedPerformanceMode
Indicates the manner or mode in which an action, process, or performance is meant or designed to be carried out.
-
B.
typicalPerformanceSetting
chosen
Indicates the usual or most common context, venue, or environment in which a performance or activity typically takes place.
-
C.
indicatedSetting
Indicates that one entity specifies, denotes, or points out a particular setting or configuration associated with another entity.
-
D.
originalIntendedSetting
Indicates the context, environment, or circumstances for which something was initially designed or meant to be used.
-
E.
intendedForPerformanceBy
Indicates that something (such as a work, role, or piece) is designed or meant to be performed by a particular performer or type of performer.
- 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_69f76e5c9b808190b486523f5c2f817d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe78e545888190a239af1a84280fa0 |
completed | May 8, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69fe7842742081908043eb950ed69f92 |
completed | May 8, 2026, 11:56 p.m. |
Created at: May 3, 2026, 4:31 p.m.