Triple
T265510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitcoin |
E5715
|
entity |
| Predicate | maxSupply |
P8885
|
FINISHED |
| Object | 21000000 BTC |
—
|
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: 21000000 BTC | Statement: [Bitcoin, maxSupply, 21000000 BTC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxSupply Context triple: [Bitcoin, maxSupply, 21000000 BTC]
-
A.
maximumService
Indicates that an entity provides the highest allowable or achievable level of service within a given context or system.
-
B.
maximumBondMaturity
Indicates the longest allowable or actual time period until a bond tied to an entity reaches its maturity date.
-
C.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
D.
supplyCut
Indicates that the normal provision or flow of a resource, product, or service to an entity has been reduced, interrupted, or stopped.
-
E.
apexOriginallyCappedBy
Indicates that the topmost point or peak of something was initially covered, sealed, or finished with a particular cap or crowning element.
- 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_69a2587daeb081909591b9d30f80a271 |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25d8f9bbc8190a13841e4de093a66 |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b6f60b081908fc6467800a8849e |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25c8ae480819094f6d1bb0a6d2eb2 |
completed | Feb. 28, 2026, 3:10 a.m. |
Created at: Feb. 28, 2026, 2:56 a.m.