Triple
T28054373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telnet Status Option |
E708919
|
entity |
| Predicate | usesSubnegotiationCommand |
P172367
|
FINISHED |
| Object | IAC SB |
—
|
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: IAC SB | Statement: [Telnet Status Option, usesSubnegotiationCommand, IAC SB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSubnegotiationCommand Context triple: [Telnet Status Option, usesSubnegotiationCommand, IAC SB]
-
A.
negotiatedWithCommand
Indicates that an entity engaged in discussions or bargaining with a command authority to reach an agreement or resolve an issue.
-
B.
usesTelnetCommand
chosen
Indicates that one entity issues or relies on a specific Telnet protocol command in its interaction with another entity.
-
C.
supportsControlSequences
Indicates that one entity is capable of recognizing and correctly handling control sequences used by another entity.
-
D.
supportsCommand
Indicates that one entity is capable of recognizing, accepting, or executing a specified command associated with another entity.
-
E.
usesAutoNegotiation
Indicates that one entity configures or operates a connection using automatic negotiation of parameters (such as speed or duplex) with 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 27, 2026, 8:35 p.m.