Triple
T1096669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SCTP |
E24285
|
entity |
| Predicate | differenceFromTCP |
P23099
|
FINISHED |
| Object | message-oriented instead of byte-stream |
—
|
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: message-oriented instead of byte-stream | Statement: [SCTP, differenceFromTCP, message-oriented instead of byte-stream]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: differenceFromTCP Context triple: [SCTP, differenceFromTCP, message-oriented instead of byte-stream]
-
A.
overheadComparedToTCP
Indicates the additional protocol or processing cost incurred by something relative to using TCP as the baseline.
-
B.
reliabilityComparedToTCP
Indicates how the reliability of one protocol or mechanism compares relative to that of TCP.
-
C.
differenceFromTAI
Indicates the degree or nature of deviation between something and a reference point defined as TAI (e.g., a target, standard, or baseline associated with TAI).
-
D.
pointDifference
Indicates the numerical difference in points or scores between two compared entities.
-
E.
dateOfTCPIPTransition
Indicates the date on which an entity transitioned its networking or communication systems to use the TCP/IP protocol.
- 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_69a4940542308190ac2a0b1f730b7cfc |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b99ffb3481908cd168b6c58e1c6d |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b7448c148190a3c9a4158ebd05b4 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b7da38888190a118ef20ce4ae9aa |
completed | March 1, 2026, 10:04 p.m. |
Created at: March 1, 2026, 7:42 p.m.