Triple
T4087665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Algorand blockchain protocol |
E87625
|
entity |
| Predicate | consensusLayer |
P49240
|
FINISHED |
| Object | on-chain |
—
|
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: on-chain | Statement: [Algorand blockchain protocol, consensusLayer, on-chain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consensusLayer Context triple: [Algorand blockchain protocol, consensusLayer, on-chain]
-
A.
consensusLayerClient
Indicates that an entity functions as or uses a client responsible for interacting with the consensus layer of a distributed or blockchain-based system.
-
B.
consensusMechanism
Indicates the method or protocol by which multiple participants in a distributed system agree on a single, consistent state or outcome.
-
C.
consensusRole
Indicates that an entity participates in a consensus process with a specific functional role (e.g., proposer, validator, leader, or follower) within that agreement mechanism.
-
D.
viewOnConsensus
Indicates the stance or opinion an entity holds regarding a consensus or commonly agreed-upon position.
-
E.
blockchain
chosen
Indicates that an entity is associated with, utilizes, or pertains to blockchain technology or distributed ledger systems.
- 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_69aed94425148190be337845d56fac22 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefca899008190b5ada98bdb79639f |
completed | March 9, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69aef909c9c88190b09d48dad325a83c |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.