Triple

T3524633
Position Surface form Disambiguated ID Type / Status
Subject Ethereum blockchain E74507 entity
Predicate hardFork P49251 FINISHED
Object Ethereum Classic split 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: Ethereum Classic split | Statement: [Ethereum blockchain, hardFork, Ethereum Classic split]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hardFork
Context triple: [Ethereum blockchain, hardFork, Ethereum Classic split]
  • A. secondHalvingYear
    Indicates the calendar year in which the second halving event of a recurring, typically periodic, process or quantity occurs.
  • B. supports64bitBlockNumbers
    Indicates that the subject is capable of handling or operating with 64-bit block number values.
  • C. thirdHalvingYear
    Indicates the calendar year in which the third occurrence of a recurring halving event (such as a scheduled reduction in rate or quantity) takes place.
  • D. difficultyTargetBits
    Indicates the required difficulty level for a task or computation, expressed as a target number of leading zero bits that a valid solution must satisfy.
  • E. firstHalvingYear
    Indicates the calendar year in which the first halving event associated with an entity (such as a cryptocurrency’s block reward) occurs.
  • 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_69ad85d0c5488190a3d8e02ebd01a1aa completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adbc68b15881909b407486946ec3c5 completed March 8, 2026, 6:14 p.m.
PD Predicate disambiguation batch_69adae121a048190b03825a001d21f49 completed March 8, 2026, 5:12 p.m.
PDg Predicate description generation batch_69adb21a437c81908bca88d5e123d744 completed March 8, 2026, 5:30 p.m.
Created at: March 8, 2026, 3:19 p.m.