Triple
T37235373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cronos Chain |
E923557
|
entity |
| Predicate | mainnetStatus |
P187669
|
FINISHED |
| Object | live |
—
|
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: live | Statement: [Cronos Chain, mainnetStatus, live]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainnetStatus Context triple: [Cronos Chain, mainnetStatus, live]
-
A.
modernStatus
Indicates the current or contemporary condition, classification, or standing of an entity in the present time.
-
B.
tetherStatus
Indicates whether one entity is currently connected to and dependent on another via a tether-like link or constraint.
-
C.
binaryStatus
Indicates that something has one of two possible states or conditions, typically representing a simple on/off or true/false status.
-
D.
MozetStatus
Indicates the current operational or state condition associated with the Mozet-related entity or process.
-
E.
kernelMainlineStatus
Indicates whether something is part of, aligned with, or supported by the mainline (upstream) version of a kernel.
- 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_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb78c982ac8190846efe8f6209e5d1 |
completed | May 6, 2026, 5:22 p.m. |
Created at: May 3, 2026, 4:15 p.m.