Triple
T18294128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frame Relay |
E438186
|
entity |
| Predicate | congestionNotificationBit |
P131223
|
FINISHED |
| Object | Forward Explicit Congestion Notification |
—
|
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: Forward Explicit Congestion Notification | Statement: [Frame Relay, congestionNotificationBit, Forward Explicit Congestion Notification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: congestionNotificationBit Context triple: [Frame Relay, congestionNotificationBit, Forward Explicit Congestion Notification]
-
A.
congestionControlAlgorithm
Indicates that one entity uses, implements, or is associated with a particular congestion control algorithm in managing network traffic.
-
B.
hasPassengerCongestionControls
Indicates that an entity includes mechanisms or measures to manage, limit, or alleviate congestion caused by passengers.
-
C.
bitSynchronizationSupport
Indicates whether a system, device, or protocol provides mechanisms to align and maintain timing at the bit level between communicating entities.
-
D.
isHopByHop
Indicates that the relationship or process occurs stepwise between directly connected intermediaries, with each node handling and forwarding it to the next rather than end-to-end.
-
E.
retransmissionCondition
Indicates the circumstances or rules under which a previously sent message, signal, or data unit should be sent again.
- 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5010205bc8190a32fe731ead3d988 |
completed | April 19, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e44fdf43d08190bbcfb6b1fe3cc0ee |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:35 a.m.