Triple
T3524627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ethereum blockchain |
E74507
|
entity |
| Predicate | decentralized |
P49250
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Ethereum blockchain, decentralized, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decentralized Context triple: [Ethereum blockchain, decentralized, true]
-
A.
distributedWith
Indicates that one entity is supplied, packaged, or made available together with another entity as part of the same distribution.
-
B.
decimalized
Indicates that something has been converted into or expressed in decimal form, typically changing from another numeral or measurement system to a base-10 representation.
-
C.
declassified
Indicates that information or material has been officially downgraded from a restricted or secret status, making it accessible to a wider audience or the public.
-
D.
deactivated
Indicates that an entity has been turned off, disabled, or rendered inactive so it no longer performs its usual function or role.
-
E.
distributedAs
Indicates that something is allocated, delivered, or spread out according to a particular pattern, rule, or distribution scheme.
- 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_69ad85d0c5488190a3d8e02ebd01a1aa |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc68b15881909b407486946ec3c5 |
completed | March 8, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69adae121a048190b03825a001d21f49 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb21a437c81908bca88d5e123d744 |
completed | March 8, 2026, 5:30 p.m. |
Created at: March 8, 2026, 3:19 p.m.