Triple
T15264208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dencun |
E364857
|
entity |
| Predicate | Deneb |
P117861
|
FINISHED |
| Object | consensus layer upgrade |
—
|
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: consensus layer upgrade | Statement: [Dencun, Deneb, consensus layer upgrade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Deneb Context triple: [Dencun, Deneb, consensus layer upgrade]
-
A.
brightestStar
Indicates that one entity is the most luminous star within a specified group, region, or context relative to the others.
-
B.
isSouthernmostStarOf
Indicates that one star occupies the southernmost position within a specified group, region, or configuration of stars.
-
C.
brightestStarAlternativeName
Indicates that an alternative or secondary name is used to refer to the same brightest star in a given context or system.
-
D.
isForegroundStarOf
Indicates that one star appears visually in front of another star along the line of sight, occupying the foreground relative to it.
-
E.
notableVariableStar
Indicates that the subject is a variable star recognized as particularly significant or noteworthy in some context (e.g., scientifically, historically, or observationally).
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0084fed0481908e452c89cba2be82 |
completed | April 15, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2ca6148190967c319728ec3661 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:14 a.m.