Triple
T9029564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zcash |
E216133
|
entity |
| Predicate | shieldedAddressPrefix |
P85759
|
FINISHED |
| Object | z |
—
|
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: z | Statement: [Zcash, shieldedAddressPrefix, z]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shieldedAddressPrefix Context triple: [Zcash, shieldedAddressPrefix, z]
-
A.
addressPrefixMainnet
Indicates that an address has the prefix format used for the main (primary/production) network.
-
B.
addressPrefix
Indicates that one address string serves as the starting portion or leading segment of another address.
-
C.
canAddress
Indicates that one entity has the ability or permission to direct communication, action, or service toward another entity.
-
D.
registrationPrefix
Indicates that an entity has a specific registration prefix code assigned to it as part of its official registration or identification.
-
E.
protectedAs
Indicates that one entity is safeguarded, preserved, or kept safe by another entity or under a specified protective status or mechanism.
- 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_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_69cc5ee3597c81908919cf866ae95c24 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f6dec4081909379bd57c02a5710 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:08 p.m.