Triple
T37150002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ava Labs |
E920336
|
entity |
| Predicate | associatedToken |
P49249
|
FINISHED |
| Object | AVAX |
E920338
|
NE FINISHED |
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: [Ava Labs, associatedToken, AVAX]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedToken Context triple: [Ava Labs, associatedToken, AVAX]
-
A.
bearerAwardAssociation
Indicates a relationship in which an entity serves as the holder or recipient associated with a particular award.
-
B.
bearerAssociatedWith
Indicates a relationship where a bearer (such as a person or entity holding something like an account, credential, or instrument) is linked or connected to another entity in a relevant context.
-
C.
associatedKey
Indicates that one entity serves as a key or identifier that is logically or functionally linked to another entity.
-
D.
nativeToken
chosen
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.
-
E.
associatedValue
Indicates that one entity is linked to another entity that serves as its corresponding or contextually related value.
- F. None of above.
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_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a402bae19848190b1de3481dfd22b00 |
completed | June 27, 2026, 7:59 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:15 p.m.