Triple
T37235365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cronos Chain |
E923557
|
entity |
| Predicate | gasToken |
P187329
|
FINISHED |
| Object | CRO |
—
|
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: CRO | Statement: [Cronos Chain, gasToken, CRO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gasToken Context triple: [Cronos Chain, gasToken, CRO]
-
A.
governanceToken
Indicates that one entity functions as a governance token for another, conferring rights to participate in decision-making or control over that entity’s governance.
-
B.
envelopeGas
Indicates that one entity serves as a surrounding gaseous layer or atmosphere enclosing another entity.
-
C.
gasBlockFeature
Indicates a feature that prevents, restricts, or controls the movement or flow of gas between entities or regions.
-
D.
gasReleased
Indicates that a gas is emitted or discharged from a source into its surrounding environment.
-
E.
feedGasSource
Indicates that one entity serves as the supplying source of gas that is fed into another entity or process.
- 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_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. |
| PDg | Predicate description generation | batch_69fb41333b548190912cb238ffc271c9 |
completed | May 6, 2026, 1:25 p.m. |
Created at: May 3, 2026, 4:15 p.m.