Triple
T37150232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C-Chain |
E920341
|
entity |
| Predicate | mainnetName |
P187482
|
FINISHED |
| Object | Avalanche C-Chain |
—
|
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 C-Chain | Statement: [C-Chain, mainnetName, Avalanche C-Chain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainnetName Context triple: [C-Chain, mainnetName, Avalanche C-Chain]
-
A.
mainnetBetaLaunchDate
Indicates the date on which the main network (mainnet) was first launched in a beta or trial phase.
-
B.
mainnetLaunchNetwork
Indicates the event or action of a network being launched on its primary (main) blockchain.
-
C.
addressPrefixMainnet
Indicates that an address has the prefix format used for the main (primary/production) network.
-
D.
testnetChainId
Indicates the identifier of the blockchain network used for testing (testnet) on which an action or relationship takes place.
-
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_69f76e9f87c08190b4c8f7fafbd8345a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69fb55dc36d08190a0634fa680e13114 |
completed | May 6, 2026, 2:53 p.m. |
Created at: May 3, 2026, 4:15 p.m.