Triple
T30407425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ZEC |
E773516
|
entity |
| Predicate | nativeBlockchain |
P169187
|
FINISHED |
| Object | Zcash |
—
|
NE NERFINISHED |
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: Zcash | Statement: [ZEC, nativeBlockchain, Zcash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nativeBlockchain Context triple: [ZEC, nativeBlockchain, Zcash]
-
A.
nativeCryptocurrency
Indicates that a cryptocurrency is the primary, built-in medium of exchange and value for a specific blockchain or distributed ledger.
-
B.
blockchain
Indicates that an entity is associated with, utilizes, or pertains to blockchain technology or distributed ledger systems.
-
C.
isPublicBlockchain
Indicates that a blockchain is open, permissionless, and accessible for anyone to read from, write to (subject to consensus rules), and participate in securing.
-
D.
supportsBlockchain
Indicates that one entity provides compatibility with, infrastructure for, or endorsement of blockchain technology used by another entity.
-
E.
chainDeveloper
Indicates a relationship where one developer depends on, extends, or builds upon the work or output of another developer in a sequential chain.
- 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_69f22490b8b48190ab10c886a8d58c89 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f686204b2c8190afea8470275fd875 |
completed | May 2, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f679496c188190ba585792f987a1f4 |
completed | May 2, 2026, 10:23 p.m. |
Created at: April 29, 2026, 8:04 p.m.