Triple
T30407059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solana |
E773507
|
entity |
| Predicate | mainnetBetaLaunchDate |
P169755
|
FINISHED |
| Object | 2020-03-16 |
—
|
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: 2020-03-16 | Statement: [Solana, mainnetBetaLaunchDate, 2020-03-16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainnetBetaLaunchDate Context triple: [Solana, mainnetBetaLaunchDate, 2020-03-16]
-
A.
mainnetLaunchYear
Indicates the calendar year in which the entity’s mainnet was officially launched.
-
B.
hardForkDate
Indicates the date on which a protocol or system undergoes a hard fork, i.e., a non-backward-compatible change that splits or upgrades the network.
-
C.
firstBlockMinedDate
Indicates the date on which the first block associated with the entity was mined.
-
D.
firstDeployedAt
Indicates the date and time when an entity was initially put into use or made operational.
-
E.
testnet
Indicates that an entity operates on, is associated with, or is designated as part of a testing blockchain network rather than the main production network.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f686204b2c8190afea8470275fd875 |
completed | May 2, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f7e116c819099aec724e9ef3763 |
completed | May 2, 2026, 10:49 p.m. |
Created at: April 29, 2026, 8:04 p.m.