Triple
T37150084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AVAX |
E920338
|
entity |
| Predicate | stakingPurpose |
P187198
|
FINISHED |
| Object | securing the Avalanche network |
—
|
LITERAL 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: securing the Avalanche network | Statement: [AVAX, stakingPurpose, securing the Avalanche network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stakingPurpose Context triple: [AVAX, stakingPurpose, securing the Avalanche network]
-
A.
derivationPurpose
Indicates that one entity is derived from another specifically in order to fulfill a particular purpose or intended use.
-
B.
entryPurpose
Indicates the reason or intended use for which an entity is being entered, accessed, or recorded in a given context.
-
C.
secretPurpose
Indicates that an entity has an underlying goal, intention, or function that is deliberately concealed or not openly disclosed.
-
D.
tagPurpose
Indicates the intended role, function, or use associated with a given tag in a particular context.
-
E.
additionalFundingPurpose
Indicates the specific reason or intended use for which additional funding is sought or allocated beyond the original amount.
- 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_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb344ba5408190a6fe8face293d88b |
completed | May 6, 2026, 12:30 p.m. |
Created at: May 3, 2026, 4:15 p.m.