Triple

T10942677
Position Surface form Disambiguated ID Type / Status
Subject Power Macintosh 6100 E258511 entity
Predicate supportsPowerPC P82507 FINISHED
Object yes 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: yes | Statement: [Power Macintosh 6100, supportsPowerPC, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsPowerPC
Context triple: [Power Macintosh 6100, supportsPowerPC, yes]
  • A. supportsIntel64
    Indicates that one entity provides compatibility with or operational support for Intel 64-bit (x86-64) architecture in relation to another entity.
  • B. supportedArchitect
    Indicates that one entity provides architectural backing, endorsement, or assistance to another entity or architectural concept.
  • C. usesArchitecture
    Indicates that one entity is built, implemented, or operates according to the architectural style, framework, or design specified by another entity.
  • D. supportsGuestArchitecture chosen
    Indicates that one entity provides the necessary capabilities or environment to run or host the specified guest architecture of another entity.
  • E. supportsBigLittleHybrid
    Indicates that an entity is compatible with or enables operation using a big.LITTLE-style heterogeneous core or component configuration.
  • 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_69d6aa8769b4819082bfe5e61b9017f0 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d770c3fb388190a598f89ae59a7b51 completed April 9, 2026, 9:26 a.m.
PD Predicate disambiguation batch_69d72e816a98819096d6c10dfb88a66a completed April 9, 2026, 4:43 a.m.
Created at: April 8, 2026, 9:23 p.m.