Triple
T9029488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RenVM |
E216131
|
entity |
| Predicate | consensus |
P55879
|
FINISHED |
| Object | Byzantine fault tolerant network of Darknodes |
—
|
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: Byzantine fault tolerant network of Darknodes | Statement: [RenVM, consensus, Byzantine fault tolerant network of Darknodes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consensus Context triple: [RenVM, consensus, Byzantine fault tolerant network of Darknodes]
-
A.
adoptedByConsensus
chosen
Indicates that a decision, action, or change was formally accepted through a consensus process among the relevant participants.
-
B.
viewOnConsensus
Indicates the stance or opinion an entity holds regarding a consensus or commonly agreed-upon position.
-
C.
agreement
Indicates that two or more parties mutually consent to and accept shared terms, conditions, or understandings.
-
D.
notAdoptedByConsensus
Indicates that a proposal, decision, or action was not accepted or approved through a consensus-based process among the relevant parties.
-
E.
commitment
Indicates a sustained obligation or promise that binds an entity to a course of action, relationship, or goal over time.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a9bcb508190b58751f1772407d4 |
completed | April 1, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee132f08190940749c7c522e4c1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:08 p.m.