Triple
T9957991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shamir secret sharing scheme |
E195491
|
entity |
| Predicate | numberOfParticipantsParameter |
P1131
|
FINISHED |
| Object | n |
—
|
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: n | Statement: [Shamir secret sharing scheme, numberOfParticipantsParameter, n]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfParticipantsParameter Context triple: [Shamir secret sharing scheme, numberOfParticipantsParameter, n]
-
A.
numberOfParticipants
chosen
Indicates the total count of entities involved in a particular event, activity, or relationship.
-
B.
vowOfParticipants
Indicates that certain participants formally promise or commit themselves to a specified action, condition, or relationship.
-
C.
hasParticipants
Indicates that an event, activity, or situation involves one or more entities as participants in it.
-
D.
numberOfMembersDeterminedBy
Indicates that the quantity of members in one entity is defined or constrained by another entity or factor.
-
E.
participantStrength
Indicates the degree or level of involvement, influence, or contribution that a participant has within a given event, interaction, or relationship.
- 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_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. |
Created at: March 30, 2026, 8:46 p.m.