Triple
T14447890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basic Attention Token |
E358253
|
entity |
| Predicate | initialCoinOffering |
P8446
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Basic Attention Token, initialCoinOffering, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialCoinOffering Context triple: [Basic Attention Token, initialCoinOffering, yes]
-
A.
coinIssuer
Indicates that an entity issues, mints, or is responsible for the creation and release of a particular coin or currency.
-
B.
coinOrPopularize
Indicates that an entity either originally creates and names a term or concept, or helps make an existing term or concept widely known and commonly used.
-
C.
OSFundInitialCapital
Indicates that an operating system fund has received its initial capital investment or starting funding amount.
-
D.
coinedIn
Indicates that something (typically a term, phrase, or name) was first created or introduced at a particular time or in a particular place.
-
E.
marketDebut
chosen
Indicates the event or point in time when something (such as a product, service, or asset) is first introduced or made available on the market.
- 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.