Triple
T30406908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Binance Smart Chain |
E773504
|
entity |
| Predicate | usesTokenForGas |
P49239
|
FINISHED |
| Object | BNB |
—
|
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: BNB | Statement: [Binance Smart Chain, usesTokenForGas, BNB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTokenForGas Context triple: [Binance Smart Chain, usesTokenForGas, BNB]
-
A.
feedGasSource
Indicates that one entity serves as the supplying source of gas that is fed into another entity or process.
-
B.
envelopeGas
Indicates that one entity serves as a surrounding gaseous layer or atmosphere enclosing another entity.
-
C.
usesTokenization
Indicates that one entity applies a tokenization process to another entity, breaking it into smaller units such as tokens or segments.
-
D.
nativeTokenOf
chosen
Indicates that a given token is the primary, built-in (native) currency or asset of a specified blockchain or platform.
-
E.
requiresBalanceWith
Indicates that one entity’s state, quantity, or action must be countered or matched by another to maintain an overall balance or equilibrium.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 29, 2026, 8:04 p.m.