Triple
T9029422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Republic Protocol |
E216130
|
entity |
| Predicate | supports |
P516
|
FINISHED |
| Object | Bitcoin Cash |
E216132
|
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 Cash | Statement: [Republic Protocol, supports, Bitcoin Cash]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bitcoin Cash Context triple: [Republic Protocol, supports, Bitcoin Cash]
-
A.
Bitcoin Cash
chosen
Bitcoin Cash is a decentralized cryptocurrency that forked from Bitcoin to offer faster, cheaper peer-to-peer payments through larger block sizes.
-
B.
Bitcoin
Bitcoin is a decentralized digital cryptocurrency that operates without a central bank, enabling peer-to-peer transactions secured by blockchain technology.
-
C.
BTC
BTC is the IATA airport code for Batticaloa Airport in Sri Lanka.
-
D.
Zcash
Zcash is a privacy-focused cryptocurrency that uses zero-knowledge proofs to enable shielded, confidential transactions on a public blockchain.
-
E.
BSV
BSV is the National Rail station code for Buckshaw Parkway railway station in Lancashire, England.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a9bcb508190b58751f1772407d4 |
completed | April 1, 2026, 12:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfeb83e8988190bf29baa1aff11ac0 |
completed | April 3, 2026, 4:32 p.m. |
Created at: March 30, 2026, 7:08 p.m.