Triple
T286778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TFTP |
E5902
|
entity |
| Predicate | reliabilityMechanism |
P10377
|
FINISHED |
| Object | stop-and-wait ARQ |
—
|
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: stop-and-wait ARQ | Statement: [TFTP, reliabilityMechanism, stop-and-wait ARQ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reliabilityMechanism Context triple: [TFTP, reliabilityMechanism, stop-and-wait ARQ]
-
A.
securityMechanism
Indicates a relationship where one entity serves as a means or method to protect another entity from threats, vulnerabilities, or unauthorized actions.
-
B.
transitionMechanismUsedWith
Indicates that a particular transition or change from one state to another is carried out using a specified mechanism or method.
-
C.
removalMechanism
Indicates the method or process by which something is removed, eliminated, or taken away from a system or context.
-
D.
hasCheckAndBalanceWith
Indicates that two entities mutually monitor, limit, or counterbalance each other's powers or actions to prevent dominance or abuse.
-
E.
hasCheckAndBalanceFunction
Indicates that one entity performs a checking or limiting role on another entity’s powers, providing oversight and balance within a system.
- 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a2605b372c8190831570aa6532cc96 |
completed | Feb. 28, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69a25b7a8d148190aacdcc8ccb35c7f3 |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a2605a3d988190a8872169fd8eb2e8 |
completed | Feb. 28, 2026, 3:26 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.