Triple
T22488150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Onion services |
E555944
|
entity |
| Predicate | v3Features |
P76951
|
FINISHED |
| Object | stronger cryptography |
—
|
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: stronger cryptography | Statement: [Onion services, v3Features, stronger cryptography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: v3Features Context triple: [Onion services, v3Features, stronger cryptography]
-
A.
version3Feature
chosen
Indicates that an entity is a feature specifically associated with, or introduced in, version 3 of a product or system.
-
B.
featuresIn
Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or context.
-
C.
featuresReimaginedVersionOf
Indicates that something includes or presents a newly interpreted or updated version of another existing work or element.
-
D.
featuresMode
Indicates that one entity operates in, supports, or is characterized by a particular mode or configuration specified by another entity.
-
E.
C-32BHasFeature
Indicates that an entity (such as a product, system, or component) possesses or includes a specific feature identified as C-32B.
- 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_69e11e53897c819088863779f8c50bb0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15c3e73108190be5ca89ea96a85e4 |
completed | April 29, 2026, 1:17 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:49 p.m.