Triple
T22488291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Onionoo |
E555947
|
entity |
| Predicate | inputDataSource |
P46377
|
FINISHED |
| Object | Tor network consensuses |
—
|
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: Tor network consensuses | Statement: [Onionoo, inputDataSource, Tor network consensuses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inputDataSource Context triple: [Onionoo, inputDataSource, Tor network consensuses]
-
A.
dataSourceFor
chosen
Indicates that one entity serves as the origin or provider of data that is used or consumed by another entity.
-
B.
trainingDataSource
Indicates the origin or provider from which the training data for a model or system is obtained.
-
C.
samplingSource
Indicates that one entity serves as the origin or provider from which another entity is sampled or drawn.
-
D.
mainSourceType
Indicates the primary category or kind of source from which something originates or is derived.
-
E.
inputSpecifier
Indicates a relationship where something defines, constrains, or specifies the form, type, or details of an input used in a process or system.
- 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.