Triple
T37235316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cronos (CRO) |
E923556
|
entity |
| Predicate | blockchainType |
P169756
|
FINISHED |
| Object | EVM-compatible chain token |
—
|
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: EVM-compatible chain token | Statement: [Cronos (CRO), blockchainType, EVM-compatible chain token]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blockchainType Context triple: [Cronos (CRO), blockchainType, EVM-compatible chain token]
-
A.
blockchainFamily
chosen
Indicates that one blockchain is related to another as part of the same technological or conceptual family, such as being derived from, compatible with, or closely based on it.
-
B.
blockchain
Indicates that an entity is associated with, utilizes, or pertains to blockchain technology or distributed ledger systems.
-
C.
isPublicBlockchain
Indicates that a blockchain is open, permissionless, and accessible for anyone to read from, write to (subject to consensus rules), and participate in securing.
-
D.
nativeBlockchain
Indicates that a given asset, token, or functionality is inherently built into and originates from a specific blockchain rather than being issued or bridged from another chain.
-
E.
supportsBlockchain
Indicates that one entity provides compatibility with, infrastructure for, or endorsement of blockchain technology used by another entity.
- 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_69f76ea9fee88190a589f661d95a7189 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb4134225081909fd60703b8cae397 |
completed | May 6, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69fb35bf767081908de8345358ca7f44 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.