Triple

T29388352
Position Surface form Disambiguated ID Type / Status
Subject Attribute Protocol E745310 entity
Predicate usedByHigherLayer P180037 FINISHED
Object Generic Attribute Profile 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: Generic Attribute Profile | Statement: [Attribute Protocol, usedByHigherLayer, Generic Attribute Profile]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedByHigherLayer
Context triple: [Attribute Protocol, usedByHigherLayer, Generic Attribute Profile]
  • A. hasLowerLevelUse
    Indicates that one entity is used or applied at a more detailed, specific, or subordinate level within the context of another entity’s use.
  • B. usedByFor
    Indicates that one entity makes use of another entity for a specific purpose or function.
  • C. usedByServer
    Indicates that something (such as a resource, component, or configuration) is utilized or relied upon by a server in its operation.
  • D. lowerLevelUsedFor
    Indicates that a lower-level component, resource, or abstraction is utilized to implement, support, or realize the functionality of a higher-level one.
  • E. usedByServiceTo
    Indicates that something (such as a resource, component, or feature) is utilized or consumed by a particular service to perform its functions.
  • 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_69f0a79dfabc81908755382ee47791e2 completed April 28, 2026, 12:27 p.m.
NER Named-entity recognition batch_69f7308a096081909d66a56f3c926806 completed May 3, 2026, 11:24 a.m.
PD Predicate disambiguation batch_69f72a00c5f081908b6539d15baf4e12 completed May 3, 2026, 10:57 a.m.
PDg Predicate description generation batch_69f730890a008190a882f7828f1c9162 completed May 3, 2026, 11:24 a.m.
Created at: April 28, 2026, 2:40 p.m.