Triple
T30407347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitcoin Cash |
E773514
|
entity |
| Predicate | blockTimeApprox |
P8887
|
FINISHED |
| Object | 10 minutes |
—
|
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: 10 minutes | Statement: [Bitcoin Cash, blockTimeApprox, 10 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blockTimeApprox Context triple: [Bitcoin Cash, blockTimeApprox, 10 minutes]
-
A.
approximateBlockTimeHours
Indicates the estimated number of hours it takes for a block-related event or process to complete.
-
B.
averageBlockTimeMinutes
chosen
Indicates the typical number of minutes it takes to produce or confirm one block in a given system or network.
-
C.
estimatedNumberOfBlocks
Indicates the approximate count of discrete blocks associated with or involved in the given entity or context.
-
D.
approximateBlockLength
Indicates that one entity specifies or estimates the length of a block in an approximate or non-exact manner.
-
E.
baseBlockInterval
Indicates the fundamental time span or block of duration used as the standard interval for measuring or organizing related events or actions.
- 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_69f22490b8b48190ab10c886a8d58c89 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:04 p.m.