Triple
T30406856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ren Project |
E773503
|
entity |
| Predicate | DarknodesEarn |
P169754
|
FINISHED |
| Object | fees from cross-chain transactions |
—
|
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: fees from cross-chain transactions | Statement: [Ren Project, DarknodesEarn, fees from cross-chain transactions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DarknodesEarn Context triple: [Ren Project, DarknodesEarn, fees from cross-chain transactions]
-
A.
notableMiner
Indicates that an entity is recognized as a miner of particular significance or prominence.
-
B.
nativeBlockchain
Indicates that a given asset, token, or functionality is inherently built into and originates from a specific blockchain rather than being issued or bridged from another chain.
-
C.
hasStake
Indicates that one entity holds an interest, share, or involvement—financial, strategic, or otherwise—in another entity or outcome.
-
D.
domainStipend
Indicates that a stipend or financial allowance is provided within a particular domain, context, or area of activity.
-
E.
miningAllowed
Indicates that performing mining activities is permitted under the relevant rules or conditions.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6861f3dcc8190992842a0d87b041d |
completed | May 2, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f7e116c819099aec724e9ef3763 |
completed | May 2, 2026, 10:49 p.m. |
Created at: April 29, 2026, 8:04 p.m.