Triple

T73310
Position Surface form Disambiguated ID Type / Status
Subject IEEE 802.3af E1467 entity
Predicate backwardCompatibleWith P4635 FINISHED
Object non-PoE Ethernet devices 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: non-PoE Ethernet devices | Statement: [IEEE 802.3af, backwardCompatibleWith, non-PoE Ethernet devices]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: backwardCompatibleWith
Context triple: [IEEE 802.3af, backwardCompatibleWith, non-PoE Ethernet devices]
  • A. hasLegacy
    Indicates that an entity leaves behind a lasting impact, influence, or inheritance that continues to exist or be recognized over time.
  • B. historicallyImplementedAs
    Indicates that one entity was used or realized as another entity in the past, even if that is no longer the case.
  • C. doesNotApplyRetroactivelyTo
    Indicates that a rule, law, or condition does not affect events, actions, or situations that occurred before it came into effect.
  • D. wasSupersededBy
    Indicates that one entity has been replaced or made obsolete by another entity that takes over its role or function.
  • E. backing
    Indicates providing support, endorsement, or financial/resources assistance to someone or something, often enabling or strengthening their actions or position.
  • 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_69a24c06b3bc8190aa4ac89026115efc completed Feb. 28, 2026, 1:59 a.m.
NER Named-entity recognition batch_69a252201fa481908e30791954119c17 completed Feb. 28, 2026, 2:25 a.m.
PD Predicate disambiguation batch_69a24eacfdc481909e9ff99752fd42bf completed Feb. 28, 2026, 2:10 a.m.
PDg Predicate description generation batch_69a2521ed5088190bbdfd22164bb4d94 completed Feb. 28, 2026, 2:25 a.m.
Created at: Feb. 28, 2026, 2:03 a.m.