Triple
T37150136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avalanche C-Chain EVM |
E920339
|
entity |
| Predicate | testnetName |
P117852
|
FINISHED |
| Object | Avalanche Fuji 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 Fuji C-Chain | Statement: [Avalanche C-Chain EVM, testnetName, Avalanche Fuji C-Chain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testnetName Context triple: [Avalanche C-Chain EVM, testnetName, Avalanche Fuji C-Chain]
-
A.
testnet
chosen
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.
-
B.
testnetChainId
Indicates the identifier of the blockchain network used for testing (testnet) on which an action or relationship takes place.
-
C.
testName
Indicates that an entity is identified or labeled by a specific test name.
-
D.
testCodeName
Indicates that an entity is identified or referred to by a specific test code name.
-
E.
thirdTestName
Indicates that an entity is associated with the name or label of its third test in a sequence of tests.
- 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_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. |
Created at: May 3, 2026, 4:15 p.m.