Triple
T30407333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitcoin Cash |
E773514
|
entity |
| Predicate | forkReason |
P19352
|
FINISHED |
| Object | scaling debate in Bitcoin community |
—
|
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: scaling debate in Bitcoin community | Statement: [Bitcoin Cash, forkReason, scaling debate in Bitcoin community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forkReason Context triple: [Bitcoin Cash, forkReason, scaling debate in Bitcoin community]
-
A.
forkOf
Indicates that one entity is a copy or derivative of another, typically created by branching from the original’s state or version.
-
B.
reasonForSplit
chosen
Indicates the cause, motivation, or circumstance that led to a separation or breakup between entities.
-
C.
fallCause
Indicates that one event or condition causes or brings about another event of falling or decline.
-
D.
migrationCause
Indicates the reason or driving factor that leads an entity to migrate from one place to another.
-
E.
failureCause
Indicates that one event, condition, or factor is the reason or source that caused a particular failure to occur.
- 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_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. |
Created at: April 29, 2026, 8:04 p.m.