Triple
T29078414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SNMPv2-TC |
E736005
|
entity |
| Predicate | textualConventionPrefix |
P165977
|
FINISHED |
| Object | conventions for common SNMP data representations |
—
|
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: conventions for common SNMP data representations | Statement: [SNMPv2-TC, textualConventionPrefix, conventions for common SNMP data representations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textualConventionPrefix Context triple: [SNMPv2-TC, textualConventionPrefix, conventions for common SNMP data representations]
-
A.
standardPrefix
Indicates that one entity serves as the conventional or officially recognized prefix used before another entity.
-
B.
namespacePrefix
Indicates the abbreviated prefix string associated with a particular namespace URI in a naming or identifier system.
-
C.
definesMIBFor
Indicates that one entity specifies or establishes the Management Information Base (MIB) used by another entity.
-
D.
tagPrefix
Indicates that one tag string serves as the starting substring (prefix) of another tag string in a tagging or labeling context.
-
E.
namingConventionType
Indicates the specific style or set of rules used for naming entities or elements in a given context.
- 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_69f077e9b0a48190bb79548279cb7f64 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6614183f881908c30af8bf54eeb59 |
completed | May 2, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65ad638ac8190a17bb987fce53279 |
completed | May 2, 2026, 8:13 p.m. |
Created at: April 28, 2026, 10:24 a.m.