Triple
T27638864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pay-to-Witness-Script-Hash |
E696534
|
entity |
| Predicate | consensusEnforced |
P55879
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Pay-to-Witness-Script-Hash, consensusEnforced, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consensusEnforced Context triple: [Pay-to-Witness-Script-Hash, consensusEnforced, yes]
-
A.
supportsConsensus
Indicates that one entity endorses, upholds, or contributes to the achievement or maintenance of a shared agreement or collective decision among multiple parties.
-
B.
adoptedByConsensus
chosen
Indicates that a decision, action, or change was formally accepted through a consensus process among the relevant participants.
-
C.
notAdoptedByConsensus
Indicates that a proposal, decision, or action was not accepted or approved through a consensus-based process among the relevant parties.
-
D.
enforcedOn
Indicates that a rule, policy, or constraint is applied with authority to a particular target or subject.
-
E.
alsoEnforcedBy
Indicates that the same rule, policy, or constraint is enforced by an additional authority, mechanism, or entity beyond the primary one.
- 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.