Triple
T37149387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 5048 |
E920322
|
entity |
| Predicate | updatesProtocolSuite |
P1215
|
FINISHED |
| Object | iWARP |
—
|
NE NERFINISHED |
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: iWARP | Statement: [RFC 5048, updatesProtocolSuite, iWARP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: updatesProtocolSuite Context triple: [RFC 5048, updatesProtocolSuite, iWARP]
-
A.
updateProtocol
Indicates that an entity modifies or revises an existing protocol, procedure, or set of rules to a newer or improved version.
-
B.
updatesProtocolBehaviorOf
Indicates that one entity modifies or changes the protocol behavior or operational rules of another entity.
-
C.
usesProtocolSuite
chosen
Indicates that one entity operates or communicates by employing the set of communication protocols defined by another entity’s protocol suite.
-
D.
updatesVersionOf
Indicates that one entity is a newer or modified version that replaces or supersedes another entity.
-
E.
upgradeMethod
Indicates the method or process by which something is improved, updated, or elevated to a higher level or version.
- 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_69f76e9f87c08190b4c8f7fafbd8345a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:15 p.m.