Triple
T32542060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blakley secret sharing scheme |
E831737
|
entity |
| Predicate | representsSecretAs |
P72867
|
FINISHED |
| Object | point in a vector space |
—
|
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: point in a vector space | Statement: [Blakley secret sharing scheme, representsSecretAs, point in a vector space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsSecretAs Context triple: [Blakley secret sharing scheme, representsSecretAs, point in a vector space]
-
A.
representsAs
chosen
Indicates that one entity serves as a depiction, symbol, or stand-in for another entity in some representational context.
-
B.
isSecretFrom
Indicates that certain information is intentionally withheld by one entity and not disclosed to another entity.
-
C.
canBeSecret
Indicates that something has the potential or suitability to be kept hidden or confidential from others.
-
D.
guardedSecretBy
Indicates that a secret is being protected or kept confidential by a specific entity.
-
E.
secretedBy
Indicates that a substance or product is released or produced by a particular cell, tissue, organ, or organism.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69feaa483fcc81909d8a46b38a8717bf |
completed | May 9, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69fea8c9d45c81908ccc8619e5fefac1 |
completed | May 9, 2026, 3:23 a.m. |
Created at: May 1, 2026, 1:02 a.m.