Triple
T27904091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BIP143 |
E705720
|
entity |
| Predicate | hashComponent |
P163976
|
FINISHED |
| Object | hashOutputs |
—
|
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: hashOutputs | Statement: [BIP143, hashComponent, hashOutputs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hashComponent Context triple: [BIP143, hashComponent, hashOutputs]
-
A.
hashComponent
chosen
Indicates that one entity is a constituent part used in computing the hash value of another entity.
-
B.
hashFamily
Indicates that a hash function belongs to, or is a member of, a particular family of related hash functions.
-
C.
hashFunction
Indicates a relationship where an input value is transformed into a fixed-size output (hash) according to a specific deterministic hashing algorithm.
-
D.
codenameComponent
Indicates that one entity serves as the codename or code-designation assigned to another entity as its component or identifying label.
-
E.
keyComponent
Indicates that one entity is an essential or foundational part required for the proper function, structure, or identity of another entity.
- 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_69ef96b5aad08190be36a277c31e7004 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 6:44 p.m.