Triple
T37150158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avalanche C-Chain EVM |
E920339
|
entity |
| Predicate | mainnetLaunchNetwork |
P187202
|
FINISHED |
| Object | Avalanche mainnet |
—
|
NE NERFINISHED |
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: Avalanche mainnet | Statement: [Avalanche C-Chain EVM, mainnetLaunchNetwork, Avalanche mainnet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainnetLaunchNetwork Context triple: [Avalanche C-Chain EVM, mainnetLaunchNetwork, Avalanche mainnet]
-
A.
mainnetBetaLaunchDate
Indicates the date on which the main network (mainnet) was first launched in a beta or trial phase.
-
B.
mainnetLaunchYear
Indicates the calendar year in which the entity’s mainnet was officially launched.
-
C.
networkDebut
Indicates the first public appearance or launch of something within a particular network or broadcasting platform.
-
D.
nativeBlockchain
Indicates that a given asset, token, or functionality is inherently built into and originates from a specific blockchain rather than being issued or bridged from another chain.
-
E.
laterNetwork
Indicates that one network occurs or is established after another network in time.
- 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_69f76e9f87c08190b4c8f7fafbd8345a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb344ba5408190a6fe8face293d88b |
completed | May 6, 2026, 12:30 p.m. |
Created at: May 3, 2026, 4:15 p.m.