Triple

T13636557
Position Surface form Disambiguated ID Type / Status
Subject The Addition of Explicit Congestion Notification (ECN) to IP E325862 entity
Predicate replacesField P28532 FINISHED
Object Type of Service field in IPv4 header 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: Type of Service field in IPv4 header | Statement: [The Addition of Explicit Congestion Notification (ECN) to IP, replacesField, Type of Service field in IPv4 header]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: replacesField
Context triple: [The Addition of Explicit Congestion Notification (ECN) to IP, replacesField, Type of Service field in IPv4 header]
  • A. replacedWith
    Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
  • B. replacesWord
    Indicates that one word is substituted for another word in a given context or expression.
  • C. replacesComponentOf chosen
    Indicates that one entity takes the place of a specific component within another entity, substituting for that component in its role or function.
  • D. replacementName
    Indicates that one entity serves as a substitute or successor name for another entity, effectively replacing the original designation.
  • E. placedBy
    Indicates that one entity was positioned, set, or put in a location or context by another entity.
  • 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_69d8076beddc8190a53156f5bea77f5e completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbc60635d08190899806fe8936f02a completed April 12, 2026, 4:19 p.m.
PD Predicate disambiguation batch_69dbbe85e1c4819095194f4b7f9f6118 completed April 12, 2026, 3:47 p.m.
Created at: April 9, 2026, 9:51 p.m.