Triple
T27638850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pay-to-Witness-Script-Hash |
E696534
|
entity |
| Predicate | addressEncoding |
P163510
|
FINISHED |
| Object | Bech32m not used for v0 |
—
|
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: Bech32m not used for v0 | Statement: [Pay-to-Witness-Script-Hash, addressEncoding, Bech32m not used for v0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressEncoding Context triple: [Pay-to-Witness-Script-Hash, addressEncoding, Bech32m not used for v0]
-
A.
addressFormat
Indicates the standardized structure or pattern in which an address’s components are arranged and written.
-
B.
addressMappingType
Indicates the specific way in which one address is associated with, translated to, or mapped onto another address or address space.
-
C.
addressLength
Indicates the length or number of characters in an address.
-
D.
addressMode
Indicates how data or resources are accessed or referenced within a system, such as the method or scheme used to locate them.
-
E.
addressType
Indicates the specific kind or category of address associated with an entity (e.g., home, work, billing, or shipping).
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6397b64f881909d811225e57aac5e |
completed | May 2, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63893cc188190883ac9321a95d2dc |
completed | May 2, 2026, 5:46 p.m. |
Created at: April 27, 2026, 2:25 p.m.