Triple

T14315088
Position Surface form Disambiguated ID Type / Status
Subject Ethernet switch E354934 entity
Predicate forwardsBasedOn P12563 FINISHED
Object destination MAC address 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: destination MAC address | Statement: [Ethernet switch, forwardsBasedOn, destination MAC address]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: forwardsBasedOn
Context triple: [Ethernet switch, forwardsBasedOn, destination MAC address]
  • A. basedOnBy
    Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
  • B. areBasedOn
    Indicates that one entity is founded, derived, or developed from the principles, content, or structure of another entity.
  • C. bestForward
    Indicates that the subject is considered the most effective or outstanding forward (e.g., in an offensive or attacking role) relative to a given group or context.
  • D. numberOfForwards
    Indicates the count of times something (such as a message, document, or item) has been forwarded from one entity to others.
  • E. routingBasis chosen
    Indicates the principle or criterion used to determine how something is directed, routed, or assigned among possible paths or destinations.
  • 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_69d8278ed42c8190b9f882dcce611347 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de85b49e5481909b9ffab2d922e284 completed April 14, 2026, 6:21 p.m.
PD Predicate disambiguation batch_69de2a9515f4819081aabf251bca5878 completed April 14, 2026, 11:52 a.m.
Created at: April 10, 2026, 1:12 a.m.