Triple
T30407011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fantom |
E773506
|
entity |
| Predicate | supportsDeFi |
P207266
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Fantom, supportsDeFi, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDeFi Context triple: [Fantom, supportsDeFi, true]
-
A.
supportsBlockchain
Indicates that one entity provides compatibility with, infrastructure for, or endorsement of blockchain technology used by another entity.
-
B.
supportsCryptocurrency
Indicates that an entity accepts or is compatible with the use, processing, or handling of cryptocurrency.
-
C.
supportsSmartContractsVia
Indicates that one entity provides smart contract functionality through or by means of another entity.
-
D.
supportsConsensus
Indicates that one entity endorses, upholds, or contributes to the achievement or maintenance of a shared agreement or collective decision among multiple parties.
-
E.
supportsFiatOnRamp
Indicates that an entity provides or enables a way to convert traditional (fiat) currency into digital assets within its system or platform.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 8:04 p.m.