Triple
T23269415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CUORE |
E588246
|
entity |
| Predicate | QValueOfDecaySearched |
P151608
|
FINISHED |
| Object | about 2527 keV |
—
|
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: about 2527 keV | Statement: [CUORE, QValueOfDecaySearched, about 2527 keV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: QValueOfDecaySearched Context triple: [CUORE, QValueOfDecaySearched, about 2527 keV]
-
A.
hasObservedDecay
Indicates that an entity has witnessed, measured, or recorded the decay of another entity or system.
-
B.
defaultQValue
Indicates the standard or initial Q-value assigned to a state-action pair before any learning or updates occur in a reinforcement learning process.
-
C.
decayConstant
Indicates the proportional rate at which a quantity undergoing exponential decay decreases per unit time.
-
D.
decayMode
Indicates the specific process or pathway by which an unstable entity transforms or decays into other products.
-
E.
dotValue
Indicates that one entity has a specific scalar value obtained from the dot product (inner product) operation with another entity.
- 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_69e25d148adc819088efbf42672604e9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1957219188190b30bceffad1542da |
completed | April 29, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d8770d081908897c28b04e5faea |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 17, 2026, 4:45 p.m.