Triple
T27638831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pay-to-Witness-Script-Hash |
E696534
|
entity |
| Predicate | scriptPubKeyFormat |
P168601
|
FINISHED |
| Object | 0 <32-byte-script-hash> |
—
|
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: 0 <32-byte-script-hash> | Statement: [Pay-to-Witness-Script-Hash, scriptPubKeyFormat, 0 <32-byte-script-hash>]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptPubKeyFormat Context triple: [Pay-to-Witness-Script-Hash, scriptPubKeyFormat, 0 <32-byte-script-hash>]
-
A.
addressPrefixP2SH
Indicates that an address uses the Pay-to-Script-Hash (P2SH) prefix format, signifying it is derived from or associated with a P2SH-type script.
-
B.
addressPrefixP2PKH
Indicates that an address begins with the prefix corresponding to a Pay-to-Public-Key-Hash (P2PKH) address format.
-
C.
scriptSigContains
Indicates that a scriptSig field includes or embeds a specified piece of data, pattern, or sub-script.
-
D.
bech32HumanReadablePart
Indicates that one entity specifies the human-readable prefix portion of a Bech32-encoded string associated with another entity.
-
E.
spentFuelDestination
Indicates where spent fuel is sent or stored after it has been used.
- 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_69f67595fa7c8190b6e9f7a8c700dd97 |
completed | May 2, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f674df80b08190adb7f7531083bbb1 |
completed | May 2, 2026, 10:04 p.m. |
Created at: April 27, 2026, 2:25 p.m.