Triple
T32542070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blakley secret sharing scheme |
E831737
|
entity |
| Predicate | shareSpace |
P199816
|
FINISHED |
| Object | t-dimensional or higher-dimensional 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: t-dimensional or higher-dimensional vector space | Statement: [Blakley secret sharing scheme, shareSpace, t-dimensional or higher-dimensional vector space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shareSpace Context triple: [Blakley secret sharing scheme, shareSpace, t-dimensional or higher-dimensional vector space]
-
A.
sharesBayWith
Indicates that two locations are situated along or adjacent to the same bay.
-
B.
sharesRoomWith
Indicates that two entities occupy or use the same room at the same time.
-
C.
sharesAreaWith
Indicates that two entities occupy or overlap the same geographic or spatial area.
-
D.
sharesSystemWith
Indicates that two entities operate within or are associated with the same overarching system or environment.
-
E.
shareWith
Indicates that something is given, disclosed, or made accessible by one entity to another entity.
- F. None of above. chosen
Provenance (4 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_69ff59b33a38819086cc9aa19b81748b |
completed | May 9, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69ff587758f88190a39c2164341dc554 |
completed | May 9, 2026, 3:53 p.m. |
| PDg | Predicate description generation | batch_69ff59b1e2ac8190bb65529e9dbbb178 |
completed | May 9, 2026, 3:58 p.m. |
Created at: May 1, 2026, 1:02 a.m.