Triple
T22488128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Onion services |
E555944
|
entity |
| Predicate | usesDomainSuffix |
P148402
|
FINISHED |
| Object | .onion |
—
|
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: .onion | Statement: [Onion services, usesDomainSuffix, .onion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDomainSuffix Context triple: [Onion services, usesDomainSuffix, .onion]
-
A.
containsDomain
Indicates that one entity includes or encompasses a specific domain as part of its scope, structure, or area of applicability.
-
B.
supportsCustomDomain
Indicates that an entity provides the capability to use or configure a custom domain name instead of a default or system-assigned domain.
-
C.
recognizedAsDomain
Indicates that one entity is acknowledged or accepted as a valid or authoritative domain associated with another entity.
-
D.
indicatesDomain
Indicates a domain or area of knowledge, activity, or applicability to which something (such as a concept, resource, or entity) belongs or is relevant.
-
E.
inputDomain
Indicates that a function, process, or system accepts inputs belonging to a specified domain or set of allowable values.
- 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_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. |
| PDg | Predicate description generation | batch_69e8aa39e3388190b659d59948ebf3e6 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:49 p.m.