Triple
T36965511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heather Mason |
E914416
|
entity |
| Predicate | motionActor |
P83328
|
FINISHED |
| Object | Heather Morris |
—
|
NE NERFINISHED |
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: Heather Morris | Statement: [Heather Mason, motionActor, Heather Morris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: motionActor Context triple: [Heather Mason, motionActor, Heather Morris]
-
A.
motionCapturePerformer
chosen
Indicates a relationship where a performer provides motion data, typically through sensors or tracking, to drive the movement of a digital character or animation.
-
B.
movementRole
Indicates the specific function or capacity an entity has within a movement or motion-related activity (e.g., mover, path, source, or goal).
-
C.
movementDirector
Indicates that one entity serves as the movement director (responsible for choreographing or directing movement) for another entity, such as a performance or production.
-
D.
motionBy
Indicates that one entity undergoes movement or change in position caused or driven by another entity or agent.
-
E.
protagonistMotionCapture
Indicates that motion capture data is being recorded or applied specifically to the story’s protagonist character.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.