Triple
T32707101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rabin cryptosystem |
E836301
|
entity |
| Predicate | plaintextSpace |
P174817
|
FINISHED |
| Object | integers modulo 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: integers modulo n | Statement: [Rabin cryptosystem, plaintextSpace, integers modulo n]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plaintextSpace Context triple: [Rabin cryptosystem, plaintextSpace, integers modulo n]
-
A.
usesSpace
Indicates that one entity occupies, consumes, or makes use of physical or conceptual space associated with another entity.
-
B.
isWrittenWithSpace
Indicates that something is written or represented with spaces separating its components or elements.
-
C.
passwordSpace
Indicates the set of all possible passwords that can be formed under a given password policy or constraints.
-
D.
treatsSpaceAs
Indicates that one entity regards, handles, or interprets another entity in the same way it would handle or interpret space.
-
E.
impliesInRegularSpaces
Indicates that a property, relation, or implication that holds in a given context also holds when restricted to or interpreted within regular spaces.
- 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c852d7248190bdf8d128992668cf |
completed | May 3, 2026, 4 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c77500a08190b2bdeca33bd2ac08 |
completed | May 3, 2026, 3:56 a.m. |
Created at: May 1, 2026, 1:10 a.m.