Triple

T27904099

Position	Surface form	Disambiguated ID	Type / Status
Subject	BIP143	`E705720`	entity
Predicate	signatureFlagSupport	`P17091`	FINISHED
Object	SIGHASH_ALL SIGHASH_ALL is the default Bitcoin transaction signature hash type that commits to all inputs and outputs, ensuring the entire transaction is signed and cannot be modified without invalidating the signature.	`E705720`	NE FINISHED

How this triple was built (3 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: SIGHASH_ALL | Statement: [BIP143, signatureFlagSupport, SIGHASH_ALL]

NEDg Description generation gpt-5.1

Instruction

Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"

Input

Entity: SIGHASH_ALL
Triple: [BIP143, signatureFlagSupport, SIGHASH_ALL]

Generated description

SIGHASH_ALL is the default Bitcoin transaction signature hash type that commits to all inputs and outputs, ensuring the entire transaction is signed and cannot be modified without invalidating the signature.

PD Predicate disambiguation gpt-5-mini-2025-08-07

Target predicate: signatureFlagSupport
Context triple: [BIP143, signatureFlagSupport, SIGHASH_ALL]

A. hasSignatureBit chosen
Indicates that an entity possesses a specific bit or flag used to represent a signature or signed status in a data structure or encoding.
B. signatureMatch
Indicates that two or more items share the same or sufficiently similar signature, confirming they correspond or are equivalent in the relevant context.
C. signatureVariant
Indicates that one signature is an alternative or modified form of another signature, differing in some aspect such as content, format, or representation while remaining related.
D. signatureBehavior
Indicates a characteristic or distinctive pattern of behavior that uniquely identifies or typifies an entity.
E. signFeature
Indicates that an entity bears or displays a particular sign, symbol, or distinguishing feature.
F. None of above.

Provenance (6 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_69ef96b5aad08190be36a277c31e7004`	completed	April 27, 2026, 5:02 p.m.
NER	Named-entity recognition	`batch_69f643ed0b7481908cf25f3afec0a61d`	completed	May 2, 2026, 6:35 p.m.
NED1	Entity disambiguation (via context triple)	`batch_6a130369d0fc81909b4b2b1933440ed0`	completed	May 24, 2026, 1:55 p.m.
NEDg	Description generation	`batch_6a1304d193f48190a19d6adbf3542088`	completed	May 24, 2026, 2:01 p.m.
NED2	Entity disambiguation (via description)	`batch_6a13057d68408190bb5e5855121f5195`	completed	May 24, 2026, 2:04 p.m.
PD	Predicate disambiguation	`batch_69f641def1e88190a05bf865ced78b23`	completed	May 2, 2026, 6:26 p.m.

Created at: April 27, 2026, 6:44 p.m.