Triple
T25436575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PCLMULQDQ (not supported) |
E637387
|
entity |
| Predicate | mayBeReportedBy |
P158515
|
FINISHED |
| Object | cryptographic library self-tests |
—
|
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: cryptographic library self-tests | Statement: [PCLMULQDQ (not supported), mayBeReportedBy, cryptographic library self-tests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeReportedBy Context triple: [PCLMULQDQ (not supported), mayBeReportedBy, cryptographic library self-tests]
-
A.
mayBeReportedBy
chosen
Indicates that an event, condition, or item can potentially be reported or documented by a particular agent or source.
-
B.
mayReportTo
Indicates that one entity is permitted or allowed to have a reporting relationship to another entity, such as an employee being allowed to report to a particular manager.
-
C.
canReport
Indicates that one entity has the ability or permission to report on, or submit a report about, another entity or situation.
-
D.
reportedFor
Indicates that one entity has formally notified an authority or system about another entity’s behavior, condition, or status, typically to trigger review or action.
-
E.
mayAlsoBeCalled
Indicates that one entity can alternatively be referred to by another name or label.
- 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6e0338c8190ace22e7a6239f68d |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 1:59 p.m.