Triple
T14447894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basic Attention Token |
E358253
|
entity |
| Predicate | totalSupply |
P8885
|
FINISHED |
| Object | 1500000000 BAT |
—
|
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: 1500000000 BAT | Statement: [Basic Attention Token, totalSupply, 1500000000 BAT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: totalSupply Context triple: [Basic Attention Token, totalSupply, 1500000000 BAT]
-
A.
maxSupply
chosen
Indicates the maximum quantity of a resource, asset, or token that can ever be created or made available.
-
B.
sharesOutstanding
Indicates the total number of a company’s shares that are currently issued and held by all shareholders, excluding any shares the company has repurchased.
-
C.
totalNumberOfHolders
Indicates the total count of distinct entities that hold or possess a given asset, item, or resource.
-
D.
hasTotalNumber
Indicates that an entity is associated with a specific overall count or sum of items, elements, or units.
-
E.
totalInvestment
Indicates the overall amount of resources (typically money) committed to a particular entity, project, or activity, aggregating all individual investments involved.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de9160126c8190a2862a1a3dde1aff |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:19 a.m.