Triple
T30157820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IETF SNMPv2 working group |
E766569
|
entity |
| Predicate | usesStandardSeries |
P34873
|
FINISHED |
| Object | Request for Comments |
E5627
|
NE 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: Request for Comments | Statement: [IETF SNMPv2 working group, usesStandardSeries, Request for Comments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesStandardSeries Context triple: [IETF SNMPv2 working group, usesStandardSeries, Request for Comments]
-
A.
hasStandardSeries
chosen
Indicates that an entity is associated with, or belongs to, a designated standard series or standardized sequence.
-
B.
usesStandard
Indicates that one entity adopts, follows, or operates according to a specified standard defined by another entity or reference.
-
C.
usesSeriesFormat
Indicates that one entity presents or organizes its content according to the series format defined or provided by another entity.
-
D.
isSeriesOf
Indicates that one entity is a sequence or set of related items that collectively form a series associated with another entity.
-
E.
isStandard
Indicates that something conforms to an established norm, specification, or commonly accepted rule.
- F. None of above.
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_69f22479cd088190ab4c6f3fce39d1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a274cc58430819089c545e66291b310 |
completed | June 8, 2026, 11:14 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: April 29, 2026, 7:21 p.m.