Triple

T12621323
Position Surface form Disambiguated ID Type / Status
Subject Thunderbolt 3 (USB‑C) E301384 entity
Predicate replacesInterface P11237 FINISHED
Object Mini DisplayPort‑based Thunderbolt 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: Mini DisplayPort‑based Thunderbolt | Statement: [Thunderbolt 3 (USB‑C), replacesInterface, Mini DisplayPort‑based Thunderbolt]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: replacesInterface
Context triple: [Thunderbolt 3 (USB‑C), replacesInterface, Mini DisplayPort‑based Thunderbolt]
  • A. replacedInterface chosen
    Indicates that one interface has been substituted or superseded by another interface.
  • B. replacesComponentOf
    Indicates that one entity takes the place of a specific component within another entity, substituting for that component in its role or function.
  • C. replacedWith
    Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
  • D. replacedClass
    Indicates that one class has been superseded or substituted by another class, typically in a versioning or refactoring context.
  • E. extendsInterface
    Indicates that one interface is defined as a subtype of another interface, inheriting its contract and adding or refining its members.
  • 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_69d7bdeaf49c8190b13800111fa77ea3 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d9617b07ec8190b714f04ae6654060 completed April 10, 2026, 8:45 p.m.
PD Predicate disambiguation batch_69d960b195108190ac25bd95e644ace4 completed April 10, 2026, 8:42 p.m.
Created at: April 9, 2026, 5:14 p.m.