Triple

T34669362
Position Surface form Disambiguated ID Type / Status
Subject Sackboy E890335 entity
Predicate canWear P94968 FINISHED
Object costumes 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: costumes | Statement: [Sackboy, canWear, costumes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: canWear
Context triple: [Sackboy, canWear, costumes]
  • A. wearableBy
    Indicates that one entity is designed or suitable to be worn on the body by another entity.
  • B. wearAuthorizedFor
    Indicates that an entity is permitted or authorized to wear a specified item (such as clothing, equipment, or insignia).
  • C. mayBeWorn chosen
    Indicates that one entity is suitable or allowed to be worn by another entity, typically as clothing, accessories, or adornment.
  • D. wearerMust
    Indicates that a specified item or object is required to be worn by a particular entity under certain conditions or rules.
  • E. wearAuthorizedBy
    Indicates that one entity’s wearing or use of an item (such as clothing, uniform, or equipment) is permitted or approved by another entity.
  • 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_69f349d9c59481908b36baa0be093aea completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f722fa31248190a1c9081ce8cfa37b completed May 3, 2026, 10:27 a.m.
PD Predicate disambiguation batch_69f72157af108190880317a62e634bb0 completed May 3, 2026, 10:20 a.m.
Created at: May 1, 2026, 2:05 a.m.