Triple

T11543132
Position Surface form Disambiguated ID Type / Status
Subject Hanzo E273720 entity
Predicate mobilityTrait P11888 FINISHED
Object Can climb walls 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: Can climb walls | Statement: [Hanzo, mobilityTrait, Can climb walls]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mobilityTrait
Context triple: [Hanzo, mobilityTrait, Can climb walls]
  • A. mobilityCharacteristic chosen
    Indicates a relationship where an entity is described or classified in terms of its movement or transportation-related properties, such as how, how well, or under what conditions it can move or be moved.
  • B. mobilityComponent
    Indicates that one entity functions as a mobility-related component or module that enables or affects the movement capabilities of another entity.
  • C. mobilityRole
    Indicates the functional role or capacity an entity has in enabling, supporting, or performing movement or transportation.
  • D. supportsMobilityType
    Indicates that one entity provides compatibility with, or can function using, a specified type of mobility or movement mode.
  • E. transportationCharacteristic
    Indicates a specific property, feature, or quality that characterizes a mode, means, or instance of transportation.
  • 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_69d6aae4dfa48190a3ab0b19a159a3c5 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d886e09eec8190894069d86b79183d completed April 10, 2026, 5:13 a.m.
PD Predicate disambiguation batch_69d8087cbe7c819085680f3d67ccc978 completed April 9, 2026, 8:13 p.m.
Created at: April 8, 2026, 9:37 p.m.