Triple
T5015676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SBC |
E112735
|
entity |
| Predicate | supportsBitpoolRange |
P61514
|
FINISHED |
| Object | 2–250 (theoretical) |
—
|
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: 2–250 (theoretical) | Statement: [SBC, supportsBitpoolRange, 2–250 (theoretical)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBitpoolRange Context triple: [SBC, supportsBitpoolRange, 2–250 (theoretical)]
-
A.
supports64bitBlockNumbers
Indicates that the subject is capable of handling or operating with 64-bit block number values.
-
B.
supportsPeerToPeerTransactions
Indicates that an entity enables or facilitates direct transactions between peers without requiring an intermediary.
-
C.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
D.
supportsBlockchain
Indicates that one entity provides compatibility with, infrastructure for, or endorsement of blockchain technology used by another entity.
-
E.
supportsMultiblockAllocation
Indicates that an entity can handle allocating or managing multiple blocks of resources or memory in a single operation.
- 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_69bd4434acb8819086679dbeccc2fe54 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd732f4c5c8190b90f8e4daab458ee |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd714ecfe08190b5830cfc1c74fa17 |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd72e1b7cc8190b2e621fdf8f22e38 |
completed | March 20, 2026, 4:16 p.m. |
Created at: March 20, 2026, 1:35 p.m.