Triple
T1649194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SNMPv2c |
E35651
|
entity |
| Predicate | usesCommunityType |
P3292
|
FINISHED |
| Object | read-only community |
—
|
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: read-only community | Statement: [SNMPv2c, usesCommunityType, read-only community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCommunityType Context triple: [SNMPv2c, usesCommunityType, read-only community]
-
A.
hasCommunityType
chosen
Indicates that an entity is associated with or classified under a particular type or category of community.
-
B.
usedByCommunity
Indicates that something is utilized or adopted collectively by a particular community.
-
C.
includesCommunity
Indicates that one entity encompasses, contains, or has within it a particular community as part of its scope or composition.
-
D.
usedInCommunity
Indicates that something is employed, practiced, or applied within a particular community or communal context.
-
E.
supportsCommunity
Indicates that one entity provides assistance, resources, or encouragement that benefits a community or group.
- 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_69a8860568888190a32cd9f70acbba42 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaa0fbe984819084f8daee81ca9b67 |
completed | March 6, 2026, 9:40 a.m. |
| PD | Predicate disambiguation | batch_69a907ce4dd881909168a1e99505d4ec |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:29 p.m.