Triple
T35279249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dance Alone |
E1018888
|
entity |
| Predicate | hasStudioProduction |
P201251
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Dance Alone, hasStudioProduction, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStudioProduction Context triple: [Dance Alone, hasStudioProduction, yes]
-
A.
hasStudio
Indicates that an entity (such as a film, game, or production) is associated with or produced by a particular studio.
-
B.
hasStudiosIn
Indicates that an entity operates or maintains studio facilities located in a specified place or region.
-
C.
producedForStudio
Indicates that a work (such as a film, show, or recording) was created under contract for, and on behalf of, a particular studio.
-
D.
producedAtStudio
Indicates that a creative work was made or recorded at a specific studio location.
-
E.
collaboratedWithStudio
Indicates that an entity worked together with a studio on a shared project 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_69f76de5c4788190896ad598ae7d6bc6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffe12ee59c8190bc7da386e6d5332d |
completed | May 10, 2026, 1:36 a.m. |
| PD | Predicate disambiguation | batch_69ffe0a138bc8190a3d4b48cd579e985 |
completed | May 10, 2026, 1:34 a.m. |
| PDg | Predicate description generation | batch_69ffe12d61e0819098692270ab2625e3 |
completed | May 10, 2026, 1:36 a.m. |
Created at: May 3, 2026, 4:02 p.m.