Triple

T25617148
Position Surface form Disambiguated ID Type / Status
Subject 3DNow! E642187 entity
Predicate optimizationRequires P100 FINISHED
Object compiler or hand-written assembly support 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: compiler or hand-written assembly support | Statement: [3DNow!, optimizationRequires, compiler or hand-written assembly support]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: optimizationRequires
Context triple: [3DNow!, optimizationRequires, compiler or hand-written assembly support]
  • A. resolutionRequires
    Indicates that resolving one issue, task, or condition depends on first completing or satisfying another specified prerequisite.
  • B. requires chosen
    Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
  • C. requiresConfiguration
    Indicates that one entity depends on another to be set up or configured before it can function or be used.
  • D. comparisonRequirement
    Indicates that one entity must be evaluated or measured in relation to another according to a specified standard or criterion.
  • E. evaluationRequirement
    Indicates that one entity imposes or specifies conditions under which another entity must be assessed, tested, or evaluated.
  • 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_69e77e7a96748190b10f2699041e4e43 completed April 21, 2026, 1:41 p.m.
NER Named-entity recognition batch_69f5f9e8734c8190a214685b1647abe1 completed May 2, 2026, 1:19 p.m.
PD Predicate disambiguation batch_69f4a0f7c6008190ae8cee3e71e19b94 completed May 1, 2026, 12:47 p.m.
Created at: April 21, 2026, 5 p.m.