Triple
T9029438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Republic Protocol |
E216130
|
entity |
| Predicate | hasComponent |
P35
|
FINISHED |
| Object | Darknodes |
E216134
|
NE 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: Darknodes | Statement: [Republic Protocol, hasComponent, Darknodes]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Darknodes Context triple: [Republic Protocol, hasComponent, Darknodes]
-
A.
Darknodes
chosen
Darknodes are decentralized network nodes that power the Ren protocol by facilitating cross-chain cryptocurrency transfers and earning fees for providing this infrastructure.
-
B.
Nethermind
Nethermind is a high-performance, .NET-based Ethereum execution client used to run full nodes, validate blocks, and interact with the Ethereum network.
-
C.
BESU
BESU is a renowned engineering and science university in West Bengal, India, known for its strong technical education and research legacy.
-
D.
Besu
Besu is an open-source Java-based Ethereum client designed for enterprise and public network use, supporting both mainnet and private/permissioned blockchain deployments.
-
E.
Teku
Teku is an open-source Ethereum consensus client written in Java, designed to run Ethereum proof-of-stake validators in a secure and enterprise-friendly way.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a9bcb508190b58751f1772407d4 |
completed | April 1, 2026, 12:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfdbc289648190834031537c8ce130 |
completed | April 3, 2026, 3:24 p.m. |
Created at: March 30, 2026, 7:08 p.m.