Triple

T37720585
Position Surface form Disambiguated ID Type / Status
Subject Dragon 2 E939570 entity
Predicate canBeManuallyControlled P136384 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: [Dragon 2, canBeManuallyControlled, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: canBeManuallyControlled
Context triple: [Dragon 2, canBeManuallyControlled, true]
  • A. canBeControlledFrom
    Indicates that one entity has the ability or authority to operate, direct, or manage another entity remotely or indirectly.
  • B. isRemoteControlled
    Indicates that an entity is operated or controlled from a distance via a remote device or system.
  • C. isManualPlayable chosen
    Indicates that something can be performed or operated manually by a person, rather than automatically or by a system.
  • D. canControl
    Indicates that one entity has the ability or authority to direct, manage, or influence the behavior or state of another entity.
  • E. isPlayerControlled
    Indicates that an entity is currently being directed or controlled by a human player rather than by the system or AI.
  • 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_69f76edc208c8190bc8b9683f75e1024 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69ff8ba3f8248190bbdf8e7ec2b35093 completed May 9, 2026, 7:31 p.m.
PD Predicate disambiguation batch_69ff8b41ba988190a7332e8317d10f09 completed May 9, 2026, 7:30 p.m.
Created at: May 3, 2026, 4:18 p.m.