Triple
T7928314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GetNext |
E184122
|
entity |
| Predicate | hasPDUTypeCode |
P56964
|
FINISHED |
| Object | 1 in SNMPv1 |
—
|
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: 1 in SNMPv1 | Statement: [GetNext, hasPDUTypeCode, 1 in SNMPv1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPDUTypeCode Context triple: [GetNext, hasPDUTypeCode, 1 in SNMPv1]
-
A.
hasTypeCode
chosen
Indicates that an entity is associated with a specific type classification represented by a code.
-
B.
hasCommunicationCodeType
Indicates that an entity is associated with a specific type or category of communication code (e.g., phone, fax, email, messaging).
-
C.
hasParType
Indicates that an entity has a specific parent type or category to which it belongs.
-
D.
hasCodaTypes
Indicates that a linguistic unit (such as a syllable) possesses one or more specific types of codas in its structure.
-
E.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
- 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_69ca828fe7bc819090f52c88dcd72183 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3ac9ac4c819082cd2190fc3ce5a2 |
completed | March 31, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69cae9335f288190ba96781fd6576a2b |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:07 p.m.