Triple
T1631700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1157 |
E35269
|
entity |
| Predicate | port161Usage |
P14760
|
FINISHED |
| Object | SNMP agent requests |
—
|
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: SNMP agent requests | Statement: [RFC 1157, port161Usage, SNMP agent requests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: port161Usage Context triple: [RFC 1157, port161Usage, SNMP agent requests]
-
A.
usedOnPort
Indicates that something is applied, connected, or operates specifically on a given port.
-
B.
typicalPort
chosen
Indicates that a specified port is commonly or normally used for a given service, protocol, or application.
-
C.
portNumber
Indicates the specific communication port assigned to a network connection, service, or endpoint.
-
D.
portConfiguration
Indicates how ports are arranged, assigned, or set up for use within a system or device.
-
E.
controlledPort
Indicates that one entity has authority over or manages the operation or configuration of a specific port of 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_69a886036bc081909ff5de16dbe5e8ea |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9431af5ac8190893133f1ae490142 |
completed | March 5, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69a907c91c888190b6ed295c1a2e0977 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.