Triple
T31080771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OCSP |
E792087
|
entity |
| Predicate | responderTypicallyIs |
P20198
|
FINISHED |
| Object | certificate authority service |
—
|
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: certificate authority service | Statement: [OCSP, responderTypicallyIs, certificate authority service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: responderTypicallyIs Context triple: [OCSP, responderTypicallyIs, certificate authority service]
-
A.
respondentDescription
Indicates that a respondent is being characterized or described in some way, typically providing details or attributes about that respondent.
-
B.
typicalResponse
Indicates that an entity’s behavior, reaction, or outcome is the standard or commonly expected response in a given context or situation.
-
C.
typicalAnswerType
Indicates the usual or expected kind of entity or value that serves as an answer to a given question or query.
-
D.
respondentStatus
Indicates the current role, condition, or state of a respondent in relation to a survey, inquiry, or legal/administrative process.
-
E.
responseTool
chosen
Indicates a tool, method, or mechanism used to produce, deliver, or manage a response in a given context.
- 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_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:02 p.m.