Triple

T4476413
Position Surface form Disambiguated ID Type / Status
Subject Gigabit Ethernet E100018 entity
Predicate maintainsMTU P56780 FINISHED
Object 1500 bytes default Ethernet MTU 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: 1500 bytes default Ethernet MTU | Statement: [Gigabit Ethernet, maintainsMTU, 1500 bytes default Ethernet MTU]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: maintainsMTU
Context triple: [Gigabit Ethernet, maintainsMTU, 1500 bytes default Ethernet MTU]
  • A. maximumSegmentLength
    Indicates the greatest allowable or observed length of a segment within a given context or structure.
  • B. maintainsThrough
    Indicates that one entity preserves, upholds, or continues a state, condition, or relationship by means of another specified entity, process, or medium.
  • C. parityMaintainedWith
    Indicates that a state of equality or balance (such as value, status, or conditions) is preserved between two entities over time.
  • D. maximumNetworkSpanWithRepeaters
    Indicates the greatest distance a network signal can reliably cover when using repeaters to extend its range.
  • E. maintainedWithin
    Indicates that one entity is kept, preserved, or sustained inside the boundaries or context of another entity.
  • 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_69b34553cbe48190afa8ac1cac285b86 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b35728ed508190ba0e882fa62d8848 completed March 13, 2026, 12:15 a.m.
PD Predicate disambiguation batch_69b3563d63008190816e37027e761375 completed March 13, 2026, 12:11 a.m.
PDg Predicate description generation batch_69b35727a8ac819090420bd3e2cfbcf1 completed March 13, 2026, 12:15 a.m.
Created at: March 12, 2026, 11:35 p.m.