Triple

T515906
Position Surface form Disambiguated ID Type / Status
Subject Transmission Control Protocol E10705 entity
Predicate flowControlMechanism P3686 FINISHED
Object receiver advertised window 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: receiver advertised window | Statement: [Transmission Control Protocol, flowControlMechanism, receiver advertised window]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: flowControlMechanism
Context triple: [Transmission Control Protocol, flowControlMechanism, receiver advertised window]
  • A. flowControl chosen
    Indicates a relationship where one entity regulates, directs, or manages the rate or sequence of another entity’s operations or movement.
  • B. fareControl
    Indicates that an entity is responsible for monitoring, enforcing, or managing payment of fares for access to a service or facility.
  • C. exportControl
    Indicates that an entity is subject to rules or restrictions governing the transfer or export of goods, services, or information across borders.
  • D. hasMechanism
    Indicates that one entity operates, functions, or produces an effect through the specified mechanism or process.
  • E. flowsAt
    Indicates that a fluid or substance moves through or along a specific location, point, or region.
  • 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_69a2e84a0d08819087e01863fcd9abf1 completed Feb. 28, 2026, 1:06 p.m.
NER Named-entity recognition batch_69a2f1836b688190a60cc901a8724159 completed Feb. 28, 2026, 1:45 p.m.
PD Predicate disambiguation batch_69a2f0151e8c81909a82b58ac0515eba completed Feb. 28, 2026, 1:39 p.m.
Created at: Feb. 28, 2026, 1:12 p.m.