Triple
T37150107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AVAX |
E920338
|
entity |
| Predicate | underlyingNetworkToken |
P49239
|
FINISHED |
| Object | Avalanche network |
—
|
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 network | Statement: [AVAX, underlyingNetworkToken, Avalanche network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingNetworkToken Context triple: [AVAX, underlyingNetworkToken, Avalanche network]
-
A.
nativeToken
Indicates that the referenced token is the primary, built-in cryptocurrency or asset of a given blockchain or platform, as opposed to a secondary or issued token.
-
B.
nativeTokenOf
chosen
Indicates that a given token is the primary, built-in (native) currency or asset of a specified blockchain or platform.
-
C.
intendedNetwork
Indicates the network that an entity is planned, designed, or expected to connect to or operate within.
-
D.
usedByNetwork
Indicates that something is utilized or operated by a particular network.
-
E.
networkIdentity
Indicates that two entities share the same identity or identifier within a particular network or networking context.
- 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_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
Created at: May 3, 2026, 4:15 p.m.