Triple
T30407243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | renBCH |
E773511
|
entity |
| Predicate | wrappedFromChain |
P169183
|
FINISHED |
| Object | Bitcoin Cash mainnet |
—
|
NE NERFINISHED |
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 mainnet | Statement: [renBCH, wrappedFromChain, Bitcoin Cash mainnet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wrappedFromChain Context triple: [renBCH, wrappedFromChain, Bitcoin Cash mainnet]
-
A.
isTraditionallyWrappedWhen
Indicates that something is customarily enclosed or covered in another material or item during a particular time, event, or circumstance.
-
B.
canBeWrappedBy
Indicates that one entity is capable of being enclosed, covered, or surrounded by another entity.
-
C.
wrapBehavior
Indicates how one entity encloses, surrounds, or encapsulates another in its behavior or execution.
-
D.
canWrap
Indicates that one entity is able to enclose, cover, or surround another entity, typically forming an outer layer or container around it.
-
E.
hasChainFunction
Indicates that an entity possesses or is associated with a specific function or role within a chain or sequence of operations.
- F. None of above. chosen
Provenance (4 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_69f22490b8b48190ab10c886a8d58c89 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f686204b2c8190afea8470275fd875 |
completed | May 2, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f679496c188190ba585792f987a1f4 |
completed | May 2, 2026, 10:23 p.m. |
Created at: April 29, 2026, 8:04 p.m.