Triple
T15264181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byzantium |
E364856
|
entity |
| Predicate | consensusChange |
P55879
|
FINISHED |
| Object | hard fork activation |
—
|
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 activation | Statement: [Byzantium, consensusChange, hard fork activation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consensusChange Context triple: [Byzantium, consensusChange, hard fork activation]
-
A.
governanceChange
Indicates a change in the structure, rules, or authority of how an entity, organization, or system is governed.
-
B.
adoptedByConsensus
chosen
Indicates that a decision, action, or change was formally accepted through a consensus process among the relevant participants.
-
C.
notAdoptedByConsensus
Indicates that a proposal, decision, or action was not accepted or approved through a consensus-based process among the relevant parties.
-
D.
amendmentMechanism
Indicates the process or rules by which an agreement, document, or system can be formally changed or updated.
-
E.
changeReason
Indicates the reason or justification for a modification or change made to an entity or its state.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0084fed0481908e452c89cba2be82 |
completed | April 15, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:14 a.m.