Triple
T1724465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ext4 |
E37465
|
entity |
| Predicate | supports64bitBlockNumbers |
P31202
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [ext4, supports64bitBlockNumbers, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supports64bitBlockNumbers Context triple: [ext4, supports64bitBlockNumbers, true]
-
A.
estimatedNumberOfBlocks
Indicates the approximate count of discrete blocks associated with or involved in the given entity or context.
-
B.
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.
-
C.
block
Indicates preventing or obstructing another entity’s action, movement, or access.
-
D.
secondHalvingYear
Indicates the calendar year in which the second halving event of a recurring, typically periodic, process or quantity occurs.
-
E.
blockRewardHalvingIntervalBlocks
Indicates the number of blocks that must be mined before the block reward is reduced (halved) according to the protocol’s schedule.
- 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_69a8861acab88190bb43cde203429399 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aadb7bda1081908f2c41c520c9c55c |
completed | March 6, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69aa61c0a0288190bce9d60062a84b69 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69aadb68868c819097ec6db6194abae6 |
completed | March 6, 2026, 1:49 p.m. |
Created at: March 4, 2026, 7:30 p.m.