Triple

T20186081
Position Surface form Disambiguated ID Type / Status
Subject Link Layer Topology Discovery E492864 entity
Predicate isProprietaryAlternativeTo P139025 FINISHED
Object none 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: none | Statement: [Link Layer Topology Discovery, isProprietaryAlternativeTo, none]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isProprietaryAlternativeTo
Context triple: [Link Layer Topology Discovery, isProprietaryAlternativeTo, none]
  • A. isAlternativeTo
    Indicates that one entity can serve as a substitute or different option in place of another.
  • B. alternativeUsedBy
    Indicates that one entity serves as an alternative option or substitute that is used in place of another entity.
  • C. wasProprietaryUntil
    Indicates that something was owned or controlled as proprietary (not publicly available or open) up to a specified point in time.
  • D. containsProprietaryComponents
    Indicates that one entity includes or is composed of components that are proprietary (owned, controlled, or restricted by a particular party).
  • E. isTraditionalProductOf
    Indicates that something is a customary or historically established product originating from a particular place, culture, or group.
  • 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_69da6268a034819081cbd9ea5a1c9475 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e668f2c03c819096336462f59dba91 completed April 20, 2026, 5:57 p.m.
PD Predicate disambiguation batch_69e55b11124c8190babacf2a0fe2d057 completed April 19, 2026, 10:45 p.m.
PDg Predicate description generation batch_69e56700b1a08190ace53cf95827d72d completed April 19, 2026, 11:36 p.m.
Created at: April 11, 2026, 11:36 p.m.