Triple

T14086635
Position Surface form Disambiguated ID Type / Status
Subject RISC II E339012 entity
Predicate supportsIntegerOperations P112758 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: [RISC II, supportsIntegerOperations, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsIntegerOperations
Context triple: [RISC II, supportsIntegerOperations, true]
  • A. supportsArbitraryPrecisionArithmetic
    Indicates that the subject system or component can perform arithmetic operations with numbers of virtually unlimited size and precision, beyond fixed hardware-imposed limits.
  • B. supportsOperationsWith
    Indicates that one entity enables, facilitates, or is compatible with the execution of operations involving another entity.
  • C. supportsOperationsIn
    Indicates that one entity enables, facilitates, or backs the execution of operations within a specified context, area, or domain of another entity.
  • D. isArithmetic
    Indicates that something pertains to arithmetic operations, properties, or reasoning within the domain of numbers and basic calculations.
  • E. hasIntegralRepresentation
    Indicates that one entity can be expressed or represented as an integral involving the other entity.
  • F. None of above. chosen

Provenance (4 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_69d81c687b0c819087fd9ed4198403f8 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de5edff1b881909ea56dc2429ef2dd completed April 14, 2026, 3:36 p.m.
PD Predicate disambiguation batch_69de05b0e6c88190a819eeba0028981f completed April 14, 2026, 9:15 a.m.
PDg Predicate description generation batch_69de2398856c81908bed6070e4ca6ab1 completed April 14, 2026, 11:23 a.m.
Created at: April 9, 2026, 10:21 p.m.