Triple
T37150213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C-Chain |
E920341
|
entity |
| Predicate | EVMCompatible |
P169181
|
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: [C-Chain, EVMCompatible, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EVMCompatible Context triple: [C-Chain, EVMCompatible, true]
-
A.
isEVMCompatible
chosen
Indicates that a blockchain or platform supports running Ethereum Virtual Machine (EVM) bytecode and smart contracts in a compatible manner.
-
B.
supportsSmartContractsVia
Indicates that one entity provides smart contract functionality through or by means of another entity.
-
C.
hardForkOf
Indicates that one version or branch of a system, protocol, or codebase has diverged incompatibly from another, creating a new line of development that is no longer backward-compatible with the original.
-
D.
EIP-4844
Indicates a relationship to Ethereum’s EIP-4844 proposal, which introduces a new transaction type for temporary “blob” data to reduce layer-2 rollup costs and improve scalability.
-
E.
supports64bitBlockNumbers
Indicates that the subject is capable of handling or operating with 64-bit block number values.
- 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_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. |
Created at: May 3, 2026, 4:15 p.m.