Triple

T20938753
Position Surface form Disambiguated ID Type / Status
Subject Yamaha PW50 E515656 entity
Predicate hasProtectiveBodywork P132245 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: [Yamaha PW50, hasProtectiveBodywork, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasProtectiveBodywork
Context triple: [Yamaha PW50, hasProtectiveBodywork, true]
  • A. hasArmorPlating chosen
    Indicates that one entity is equipped with or covered by protective armor plating in relation to another entity or context.
  • B. usesArmoredVehicle
    Indicates that an entity employs or operates an armored vehicle in performing an action or fulfilling a role.
  • C. protectsBodyPart
    Indicates that one entity serves to shield, guard, or defend a specific body part from harm or damage.
  • D. providesProtectionIn
    Indicates that one entity offers protection or safeguarding to another entity within a specified context, location, or situation.
  • E. hasUndercarriageType
    Indicates the specific type or configuration of undercarriage that an object (typically a vehicle or machine) possesses.
  • 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_69e0b4fc13408190b06868df03c5c29b completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6f95419a48190b7f62abc59f38bef completed April 21, 2026, 4:13 a.m.
PD Predicate disambiguation batch_69e5c9af1fe08190953366a466950140 completed April 20, 2026, 6:37 a.m.
Created at: April 16, 2026, 12:50 p.m.