Triple
T9326413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eric Blore as Bates |
E224396
|
entity |
| Predicate | appearsInDanceFilm |
P87541
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Eric Blore as Bates, appearsInDanceFilm, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInDanceFilm Context triple: [Eric Blore as Bates, appearsInDanceFilm, true]
-
A.
hasDanceSceneWith
Indicates that two entities participate together in a dance scene within the same context or work.
-
B.
hasDanceSequences
Indicates that the subject contains or features one or more dance sequences as part of its content or activity.
-
C.
hasDanceAssociation
Indicates that there is a relationship or affiliation between an entity and a dance-related organization, group, or activity.
-
D.
choreographedIn
Indicates that an entity (typically a choreographer or group) created or arranged the choreography for a performance, work, or event in a specified context or production.
-
E.
hasDanceEnsemble
Indicates that an entity is associated with or includes a particular dance ensemble as part of its activities or composition.
- 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_69ca8427a0c08190b749831d5ea98f02 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd36f88e988190bb896a3d7c3c723c |
completed | April 1, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cc7a643924819097f01144734901cf |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc94b796788190816b71b1e9996288 |
completed | April 1, 2026, 3:44 a.m. |
Created at: March 30, 2026, 7:39 p.m.