Triple
T27638848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pay-to-Witness-Script-Hash |
E696534
|
entity |
| Predicate | bech32PrefixTestnet |
P117852
|
FINISHED |
| Object | tb1 |
—
|
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: tb1 | Statement: [Pay-to-Witness-Script-Hash, bech32PrefixTestnet, tb1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bech32PrefixTestnet Context triple: [Pay-to-Witness-Script-Hash, bech32PrefixTestnet, tb1]
-
A.
addressPrefixMainnet
Indicates that an address has the prefix format used for the main (primary/production) network.
-
B.
testnet
chosen
Indicates that an entity operates on, is associated with, or is designated as part of a testing blockchain network rather than the main production network.
-
C.
shieldedAddressPrefix
Indicates that an address begins with a specific prefix used for shielded or privacy-protecting transactions.
-
D.
BITCdisplayedAs
Indicates that one entity is visually presented or rendered in the form or style of another entity.
-
E.
chainCharacteristic
Indicates that one entity specifies a characteristic, property, or attribute of a chain associated with another entity.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 2:25 p.m.