Triple
T19401760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adam Back |
E485340
|
entity |
| Predicate | BlockstreamFocus |
P37442
|
FINISHED |
| Object | Bitcoin infrastructure |
—
|
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: Bitcoin infrastructure | Statement: [Adam Back, BlockstreamFocus, Bitcoin infrastructure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BlockstreamFocus Context triple: [Adam Back, BlockstreamFocus, Bitcoin infrastructure]
-
A.
blockchain
Indicates that an entity is associated with, utilizes, or pertains to blockchain technology or distributed ledger systems.
-
B.
chainCharacteristic
Indicates that one entity specifies a characteristic, property, or attribute of a chain associated with another entity.
-
C.
spentFuelDestination
Indicates where spent fuel is sent or stored after it has been used.
-
D.
supportsBlockchain
chosen
Indicates that one entity provides compatibility with, infrastructure for, or endorsement of blockchain technology used by another entity.
-
E.
chain
Indicates that one entity is linked or connected in sequence to another, typically as part of a series or chain of related elements or actions.
- 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62577454c81909d5bcd07e99b27e4 |
completed | April 20, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:36 p.m.