Triple
T27638889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SegWit2x |
E696535
|
entity |
| Predicate | consensusChangeType |
P38005
|
FINISHED |
| Object | hard fork |
—
|
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: hard fork | Statement: [SegWit2x, consensusChangeType, hard fork]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consensusChangeType Context triple: [SegWit2x, consensusChangeType, hard fork]
-
A.
changeType
chosen
Indicates the specific kind or category of modification that has occurred to an entity or relationship.
-
B.
governanceChange
Indicates a change in the structure, rules, or authority of how an entity, organization, or system is governed.
-
C.
changeReason
Indicates the reason or justification for a modification or change made to an entity or its state.
-
D.
changedFrom
Indicates that an entity previously had one state, value, or form and was altered or updated from that prior condition to a new one.
-
E.
typeOfAmendment
Indicates the specific kind or category of amendment that is being applied to something, such as a document, law, or agreement.
- 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_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 27, 2026, 2:25 p.m.