Triple
T31080767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OCSP |
E792087
|
entity |
| Predicate | RFC 5019Defines |
P83873
|
FINISHED |
| Object | lightweight OCSP profile |
—
|
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: lightweight OCSP profile | Statement: [OCSP, RFC 5019Defines, lightweight OCSP profile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RFC 5019Defines Context triple: [OCSP, RFC 5019Defines, lightweight OCSP profile]
-
A.
MOBIKEDefinedInRFC
Indicates that the MOBIKE protocol or mechanism is specified or formally described within a particular RFC document.
-
B.
accountingDefinedInRFC
Indicates that the accounting mechanism or specification is formally defined or described within a particular RFC (Request for Comments) document.
-
C.
hasRFC
chosen
Indicates that an entity is associated with, described by, or defined in a specific RFC (Request for Comments) document.
-
D.
originalRfc
Indicates that something is the initial or authoritative RFC (Request for Comments) document from which a specification, standard, or later revision originates.
-
E.
protocolDefined
Indicates that a specific protocol formally specifies or governs the behavior, format, or interaction associated with the related entities.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 9:02 p.m.