Triple
T10532278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SHA-256 |
E248473
|
entity |
| Predicate | usedIn |
P98
|
FINISHED |
| Object | Bitcoin |
E5715
|
NE 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 | Statement: [SHA-256, usedIn, Bitcoin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bitcoin Context triple: [SHA-256, usedIn, Bitcoin]
-
A.
Bitcoin
chosen
Bitcoin is a decentralized digital cryptocurrency that operates without a central bank, enabling peer-to-peer transactions secured by blockchain technology.
-
B.
BTC
BTC is the IATA airport code for Batticaloa Airport in Sri Lanka.
-
C.
Bitcoin Cash
Bitcoin Cash is a decentralized cryptocurrency that forked from Bitcoin to offer faster, cheaper peer-to-peer payments through larger block sizes.
-
D.
BitC
BitC is a systems programming language designed for safety, low-level control, and formal verification, drawing on ideas from Modula-3 and capability-based security.
-
E.
Zcash
Zcash is a privacy-focused cryptocurrency that uses zero-knowledge proofs to enable shielded, confidential transactions on a public blockchain.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d50a17f23081909f3372e160e21670 |
completed | April 7, 2026, 1:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d90e471e9c8190b134249073b289bd |
completed | April 10, 2026, 2:50 p.m. |
Created at: April 6, 2026, 12:30 p.m.