Triple
T27638845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pay-to-Witness-Script-Hash |
E696534
|
entity |
| Predicate | scriptVisibility |
P74023
|
FINISHED |
| Object | script revealed only on spend |
—
|
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: script revealed only on spend | Statement: [Pay-to-Witness-Script-Hash, scriptVisibility, script revealed only on spend]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptVisibility Context triple: [Pay-to-Witness-Script-Hash, scriptVisibility, script revealed only on spend]
-
A.
scriptFeature
Indicates that a script includes, supports, or is characterized by a particular feature or capability.
-
B.
visibilityStatus
chosen
Indicates the current level or state of how observable, accessible, or exposed an entity is within a given context.
-
C.
scriptOnFlag
Indicates that a script is attached to and/or executed when a specific flag or condition is set.
-
D.
isVisibleAs
Indicates that one entity can be perceived or appears to observers under the form, name, or representation of another entity.
-
E.
visibleAt
Indicates that one entity can be seen or perceived from a specific location, viewpoint, or context at a given time.
- 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_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 27, 2026, 2:25 p.m.