Triple

T1499624
Position Surface form Disambiguated ID Type / Status
Subject Intel 4004 E29765 entity
Predicate supportsSubroutines P203 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: [Intel 4004, supportsSubroutines, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsSubroutines
Context triple: [Intel 4004, supportsSubroutines, yes]
  • A. supportedParadigm
    Indicates that one entity (such as a tool, language, or system) provides functionality or features that enable or are compatible with a particular paradigm or methodological approach.
  • B. supportsFeature chosen
    Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
  • C. hasSubstrateLanguage
    Indicates a relationship where one language serves as the underlying substrate that has influenced or shaped another language.
  • D. supportsImplementationOf
    Indicates that one entity provides the necessary resources, framework, or assistance for another entity to be carried out, realized, or put into practice.
  • E. isSupportedBy
    Indicates that an entity is upheld, sustained, or enabled by another entity, which provides necessary assistance, resources, or justification.
  • 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_69a498dba1d8819093b46a3a8d2485f1 completed March 1, 2026, 7:51 p.m.
NER Named-entity recognition batch_69a4c6f0ce988190aafab4a6e0dfd710 completed March 1, 2026, 11:08 p.m.
PD Predicate disambiguation batch_69a4c48a8cf48190a6ebf8d44a608a06 completed March 1, 2026, 10:58 p.m.
Created at: March 1, 2026, 8:12 p.m.