Triple
T22499215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Certbot |
E556222
|
entity |
| Predicate | supportsValidationMethod |
P89458
|
FINISHED |
| Object | HTTP-01 |
—
|
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: HTTP-01 | Statement: [Certbot, supportsValidationMethod, HTTP-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsValidationMethod Context triple: [Certbot, supportsValidationMethod, HTTP-01]
-
A.
supportsValidationOf
Indicates that one entity provides the mechanisms or conditions necessary for another entity to be checked or verified for correctness or compliance.
-
B.
requiresValidationAt
Indicates that an entity must undergo validation at a specific point, condition, or stage in a process.
-
C.
supportsTestType
chosen
Indicates that one entity is capable of handling, executing, or being compatible with a specified type of test.
-
D.
supportsConstraint
Indicates that one entity upholds, enforces, or is compatible with a specified constraint or set of constraints in relation to another entity.
-
E.
supportsImplementationOf
Indicates that one entity provides the necessary resources, framework, or assistance for another entity to be carried out, realized, or put into practice.
- 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_69e11e5445bc8190b6a9481926db3355 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15cb3deb88190874230ae06a352d6 |
completed | April 29, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e898be31448190be5ae7f5656f0497 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:50 p.m.