Triple
T30334512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blitmap |
E771578
|
entity |
| Predicate | languageOfSmartContracts |
P18654
|
FINISHED |
| Object | Solidity |
—
|
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: Solidity | Statement: [Blitmap, languageOfSmartContracts, Solidity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfSmartContracts Context triple: [Blitmap, languageOfSmartContracts, Solidity]
-
A.
supportsSmartContractsVia
Indicates that one entity provides smart contract functionality through or by means of another entity.
-
B.
languageOfCode
chosen
Indicates that a programming code artifact is written in, or uses, a particular programming language.
-
C.
isEVMCompatible
Indicates that a blockchain or platform supports running Ethereum Virtual Machine (EVM) bytecode and smart contracts in a compatible manner.
-
D.
languageOfImplementation
Indicates the programming language in which a given software system, component, or algorithm is implemented.
-
E.
languageOfOperation
Indicates the language in which an entity (such as a system, service, or process) primarily operates or functions.
- 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_69f2248aba24819095bb86480d55b23b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff069ec1348190815375c5c9e38404 |
completed | May 9, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69ff05ba57f88190a45d20f18044e0fb |
completed | May 9, 2026, 10 a.m. |
Created at: April 29, 2026, 7:54 p.m.