Triple
T37150088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AVAX |
E920338
|
entity |
| Predicate | supplyPolicy |
P187200
|
FINISHED |
| Object | capped maximum supply |
—
|
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: capped maximum supply | Statement: [AVAX, supplyPolicy, capped maximum supply]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supplyPolicy Context triple: [AVAX, supplyPolicy, capped maximum supply]
-
A.
shippingPolicy
Indicates the rules and conditions governing how items are shipped, including methods, costs, and delivery terms between parties.
-
B.
subscriptionPolicy
Indicates the rules, terms, and conditions that govern how a subscription is obtained, used, renewed, or terminated between parties.
-
C.
supportPolicy
Indicates that one entity endorses, backs, or helps to maintain a particular policy or course of action.
-
D.
paymentPolicy
Indicates the rules, terms, and conditions governing how payments are expected to be made between the related parties.
-
E.
settlementPolicy
Indicates the rules or arrangements governing how and when obligations, transactions, or disputes between parties are finalized and settled.
- 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.