Triple
T591793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Probabilistic Encryption |
E17287
|
entity |
| Predicate | wasFormalizedIn |
P6279
|
FINISHED |
| Object | 1980s |
—
|
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: 1980s | Statement: [Probabilistic Encryption, wasFormalizedIn, 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFormalizedIn Context triple: [Probabilistic Encryption, wasFormalizedIn, 1980s]
-
A.
isFormalizedBy
Indicates that something is given a defined, structured, or official form through a specific method, process, or representation.
-
B.
termFormalizedBy
chosen
Indicates that a given term has been formally defined, specified, or codified by a particular formalization (such as a formal theory, document, or system).
-
C.
conventionAdoptedAt
Indicates that a convention was formally adopted or agreed upon at a specific event, meeting, or location.
-
D.
believedToBeInstitutedBy
Indicates that something is thought or assumed to have been established, founded, or created by a particular agent or entity.
-
E.
codifiedIn
Indicates that something is formally recorded, defined, or established within a specific document, code, or legal/institutional text.
- 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_69a49379d09c8190ac7e00b24e2810b1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49bbaf53081908eed240bed09f63b |
completed | March 1, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69a494cc13988190892ca10bd7ae9f09 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.