Triple
T37150148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avalanche C-Chain EVM |
E920339
|
entity |
| Predicate | feeToken |
P49255
|
FINISHED |
| Object | AVAX |
—
|
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: AVAX | Statement: [Avalanche C-Chain EVM, feeToken, AVAX]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feeToken Context triple: [Avalanche C-Chain EVM, feeToken, AVAX]
-
A.
feeUnit
chosen
Indicates the unit of measurement or currency in which a fee amount is expressed.
-
B.
isFeePaying
Indicates that an entity is required to pay a fee in order to participate in, access, or receive a specified service, resource, or activity.
-
C.
feeStatus
Indicates the current state or condition of fees associated with an entity, such as whether they are due, paid, waived, or overdue.
-
D.
feeType
Indicates the specific category or classification of a fee associated with a transaction, service, or obligation.
-
E.
feeAccess
Indicates that access to something is granted only upon payment of a fee or charge.
- 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_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:15 p.m.