Triple

T38590911
Position Surface form Disambiguated ID Type / Status
Subject Au Ra E932449 entity
Predicate canBeClass P14124 FINISHED
Object any combat class 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: any combat class | Statement: [Au Ra, canBeClass, any combat class]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: canBeClass
Context triple: [Au Ra, canBeClass, any combat class]
  • A. canBeTypeOf chosen
    Indicates that one entity is capable of serving as, or being classified as, a particular type or category of another entity.
  • B. isClass
    Indicates that an entity functions as a class or type definition within a classification or type system.
  • C. isClassOf
    Indicates that one entity is a class or category to which another entity belongs or is an instance of.
  • D. canBeDefinedFor
    Indicates that a certain concept, operation, or property is applicable to and can be meaningfully specified for a given entity or set of entities.
  • E. usesClass
    Indicates that one entity makes use of, depends on, or is implemented using a particular class in its structure or behavior.
  • 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_69f76ec654d48190b421111cf26e54d9 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69ffbb1c5bf88190a0bf791213045885 completed May 9, 2026, 10:54 p.m.
PD Predicate disambiguation batch_69ffba0ab0f881908f84ef81f7a1bfe8 completed May 9, 2026, 10:49 p.m.
Created at: May 3, 2026, 4:32 p.m.