Triple
T17051503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verifiable Random Function |
E413706
|
entity |
| Predicate | evaluationUses |
P77543
|
FINISHED |
| Object | secret key |
—
|
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: secret key | Statement: [Verifiable Random Function, evaluationUses, secret key]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evaluationUses Context triple: [Verifiable Random Function, evaluationUses, secret key]
-
A.
evaluationUse
chosen
Indicates that something is used as a basis, tool, or resource for evaluating or assessing something else.
-
B.
evaluationModel
Indicates a relationship where one entity serves as a model, standard, or framework used to assess, judge, or measure the performance or quality of another entity.
-
C.
evaluationAspect
Indicates the specific dimension or criterion of performance or quality that is being assessed within an evaluation.
-
D.
evaluationRole
Indicates the role or capacity in which an entity participates in an evaluation or assessment process.
-
E.
evaluationBasis
Indicates the criteria, standards, or reference framework used to judge, assess, or measure something in an evaluation process.
- 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_69d886cde3d481908d4d01ba88ba7eb7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3daa26e84819098b41ae15618e813 |
completed | April 18, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69e35d60a588819084f53ef9f8b2e7c0 |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:34 a.m.