Triple
T30407457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ZEC |
E773516
|
entity |
| Predicate | transactionTypes |
P27343
|
FINISHED |
| Object | shielded-to-shielded |
—
|
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: shielded-to-shielded | Statement: [ZEC, transactionTypes, shielded-to-shielded]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transactionTypes Context triple: [ZEC, transactionTypes, shielded-to-shielded]
-
A.
transactionNature
Indicates the type or character of a transaction, specifying what kind of exchange or operation is taking place between the involved parties.
-
B.
transactionModel
Indicates a relationship where an entity uses or is governed by a specific structured framework or schema for conducting, recording, or managing transactions.
-
C.
transaction
Indicates a transfer of value or assets between parties, typically involving an exchange such as payment for goods or services.
-
D.
transactionField
Indicates that a specific data field is associated with, or belongs to, a particular transaction.
-
E.
transferType
chosen
Indicates the specific method or category of how something is transferred from one entity to another.
- 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_69f22490b8b48190ab10c886a8d58c89 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdd92396788190ae1424bc1ae55844 |
completed | May 8, 2026, 12:37 p.m. |
| PD | Predicate disambiguation | batch_69fdd678f40481909a717a2daec83b36 |
completed | May 8, 2026, 12:26 p.m. |
Created at: April 29, 2026, 8:04 p.m.