Triple
T10035230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SNMP-PROXY-MIB |
E204948
|
entity |
| Predicate | hasOIDPrefix |
P66954
|
FINISHED |
| Object | 1.3.6.1.6.3.14 |
—
|
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.3.6.1.6.3.14 | Statement: [SNMP-PROXY-MIB, hasOIDPrefix, 1.3.6.1.6.3.14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOIDPrefix Context triple: [SNMP-PROXY-MIB, hasOIDPrefix, 1.3.6.1.6.3.14]
-
A.
hasOriginalPrefix
Indicates that an entity retains or is associated with its initial or primary prefix from which later forms or variants are derived.
-
B.
hasPrefix
chosen
Indicates that one entity occurs at the beginning of another entity, serving as its starting segment or initial substring.
-
C.
hasStationCodePrefix
Indicates that one entity’s station code begins with the prefix specified by the other entity.
-
D.
haveIdentifier
Indicates that an entity is associated with a specific identifier used to uniquely reference or distinguish it.
-
E.
namespacePrefix
Indicates the abbreviated prefix string associated with a particular namespace URI in a naming or identifier system.
- 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_69ca834d77188190ad645e33e8ca3200 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdce4a515c8190baec86d924623b12 |
completed | April 2, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8638508190b22acc65500ec7d6 |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:55 p.m.