Triple

T32342163
Position Surface form Disambiguated ID Type / Status
Subject Arnold Cunningham E826344 entity
Predicate stageDirectionTrait P174879 FINISHED
Object physically clumsy 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: physically clumsy | Statement: [Arnold Cunningham, stageDirectionTrait, physically clumsy]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: stageDirectionTrait
Context triple: [Arnold Cunningham, stageDirectionTrait, physically clumsy]
  • A. stageDirectionType
    Indicates the specific kind or category of stage direction associated with a performance element or action.
  • B. stageDirectionName
    Indicates the specific label or term used to identify a particular stage direction within a performance or script.
  • C. stageDirectionDescription
    Indicates a textual description of how an action, movement, or expression should be performed or presented within a staged or scripted context.
  • D. stageDirectionDescribedAs
    Indicates that a stage direction is characterized or specified using a particular textual description or phrasing.
  • E. stageDirector
    Indicates a relationship where one entity serves as the stage director responsible for overseeing and coordinating the staging of a performance involving another entity.
  • 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_69f34914dfc48190a390cd0720d9e86f completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6c90790788190a1ed09adc86ed22d completed May 3, 2026, 4:03 a.m.
PD Predicate disambiguation batch_69f6c3f42fbc8190a06eb1044c9e6094 completed May 3, 2026, 3:41 a.m.
PDg Predicate description generation batch_69f6c814c26c81908f5c47285129ff2a completed May 3, 2026, 3:59 a.m.
Created at: May 1, 2026, 12:48 a.m.