Triple
T30369206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DeFi |
E772504
|
entity |
| Predicate | typicallyRunsOn |
P121617
|
FINISHED |
| Object | public blockchains |
—
|
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: public blockchains | Statement: [DeFi, typicallyRunsOn, public blockchains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyRunsOn Context triple: [DeFi, typicallyRunsOn, public blockchains]
-
A.
systemOperatesOn
Indicates that a system performs operations, actions, or processing directly on a specified target or resource.
-
B.
worksOnPlatform
chosen
Indicates that an entity performs its functions, operations, or activities using or within a specified platform.
-
C.
runsOnHardware
Indicates that a system, software, or process operates using or is executed on a specified hardware platform.
-
D.
developsOnPlatform
Indicates that one entity is created, built, or developed using the tools, services, or environment provided by another platform entity.
-
E.
operatedOnSystem
Indicates that an entity has performed operations or actions upon a particular system, affecting its state or behavior.
- 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 7:59 p.m.