Triple

T33775201
Position Surface form Disambiguated ID Type / Status
Subject Oathkeeper E865496 entity
Predicate canCut P60772 FINISHED
Object armor 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: armor | Statement: [Oathkeeper, canCut, armor]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: canCut
Context triple: [Oathkeeper, canCut, armor]
  • A. hasCut
    Indicates that one entity has made or possesses a cut in, on, or through another entity.
  • B. isCutInto
    Indicates that one entity is divided or separated into pieces or segments that become the other entity.
  • C. hasTypicalCut
    Indicates that one entity is characterized by or associated with a standard or typical type of cut of another entity.
  • D. canSplit chosen
    Indicates that an entity has the ability or is allowed to divide something into two or more parts.
  • E. cuttingResultedIn
    Indicates that an act of cutting caused or produced a particular outcome, state, or resulting object.
  • 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_69f3498df6f88190bf9647ea4e4a956e completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6ffbad8848190867c2988c0ceb84f completed May 3, 2026, 7:56 a.m.
PD Predicate disambiguation batch_69f6fc5740fc81909774a4f65201a3ff completed May 3, 2026, 7:42 a.m.
Created at: May 1, 2026, 1:45 a.m.