Triple
T9958000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shamir secret sharing scheme |
E195491
|
entity |
| Predicate | shareSize |
P91653
|
FINISHED |
| Object | each share has size equal to the secret size |
—
|
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: each share has size equal to the secret size | Statement: [Shamir secret sharing scheme, shareSize, each share has size equal to the secret size]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shareSize Context triple: [Shamir secret sharing scheme, shareSize, each share has size equal to the secret size]
-
A.
sharesBaseWith
Indicates that two entities have a common underlying base element, source, or component from which they are derived or constructed.
-
B.
sharesIn
Indicates that one entity holds or possesses shares or ownership stakes in another entity.
-
C.
sharesBayWith
Indicates that two locations are situated along or adjacent to the same bay.
-
D.
sharesItem
Indicates that one entity provides access to or distributes an item to another entity.
-
E.
sharesSystemWith
Indicates that two entities operate within or are associated with the same overarching system or environment.
- 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_69ca82eaaa008190a54fa1a9f954b9ad |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb6cceb608190ad4424afaddcabfa |
completed | April 2, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9ae19c819099fb3635e57c79be |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd36f112bc81908b473787e702de2f |
completed | April 1, 2026, 3:17 p.m. |
Created at: March 30, 2026, 8:46 p.m.