Triple
T27638906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SegWit2x |
E696535
|
entity |
| Predicate | wouldCause |
P146054
|
FINISHED |
| Object | chain split risk |
—
|
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: chain split risk | Statement: [SegWit2x, wouldCause, chain split risk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wouldCause Context triple: [SegWit2x, wouldCause, chain split risk]
-
A.
wouldProvide
Indicates that one entity is willing or expected to supply or furnish something to another entity under certain conditions.
-
B.
possibleCauseOf
chosen
Indicates that one entity is a potential, but not certain, cause or contributing factor to another entity or outcome.
-
C.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
D.
willKill
Indicates that one entity is destined or intends to cause the death of another entity in the future.
-
E.
couldIssue
Indicates that one entity has the authority or ability to issue something (such as a document, command, or resource) to another entity.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6318fec0c8190971b4fc1a7df10d3 |
completed | May 2, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:25 p.m.