Triple

T29752796
Position Surface form Disambiguated ID Type / Status
Subject STD 37 E752945 entity
Predicate isCoreSpecificationOf P5374 FINISHED
Object Internet architecture NE NERFINISHED

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: Internet architecture | Statement: [STD 37, isCoreSpecificationOf, Internet architecture]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isCoreSpecificationOf
Context triple: [STD 37, isCoreSpecificationOf, Internet architecture]
  • A. isCoreComponentOf
    Indicates that something is an essential, foundational part required for the structure, function, or identity of another entity.
  • B. hasSpecification chosen
    Indicates that an entity is associated with a particular specification that defines or constrains its properties, behavior, or requirements.
  • C. extendsSpecificationDefinedIn
    Indicates that one specification builds upon, elaborates, or broadens the scope of another previously defined specification.
  • D. isSpecializedFor
    Indicates that one entity is specifically adapted, designed, or focused to perform optimally for a particular function, context, or domain associated with another entity.
  • E. isFeatureOf
    Indicates that something functions as a characteristic, attribute, or component belonging to or describing another entity.
  • 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_69f0d62c84cc8190846f80ae04fdf8ec completed April 28, 2026, 3:45 p.m.
NER Named-entity recognition batch_69f6736b9c748190a53ea1b926c7cc5b completed May 2, 2026, 9:58 p.m.
PD Predicate disambiguation batch_69f66ac1a4fc81909740d2e52fbe6970 completed May 2, 2026, 9:21 p.m.
Created at: April 28, 2026, 7:54 p.m.