Triple
T15581897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type Ia supernovae |
E374518
|
entity |
| Predicate | typicalRiseTime |
P6833
|
FINISHED |
| Object | about 17–20 days to B-band maximum |
—
|
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 17–20 days to B-band maximum | Statement: [Type Ia supernovae, typicalRiseTime, about 17–20 days to B-band maximum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRiseTime Context triple: [Type Ia supernovae, typicalRiseTime, about 17–20 days to B-band maximum]
-
A.
hasSlewRateTypical
Indicates that an entity is characterized by a specified typical (nominal) slew rate value.
-
B.
typicalRuntimeRange
Indicates the usual lower and upper bounds of time typically required for an entity to run or complete its operation.
-
C.
timeOfRise
Indicates the specific time at which something begins to rise or appear, such as a celestial body or similar phenomenon.
-
D.
typicalTimes
chosen
Indicates the usual or characteristic times at which an event, activity, or condition typically occurs.
-
E.
typicalTestDuration
Indicates the usual or expected length of time required to complete a given test.
- 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_69d85ccd575081908909b71a3f3e3a61 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e45ee3c8190a6aee06a5805ca39 |
completed | April 16, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69deda817e9881909b0c66fc9056f7d5 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:11 a.m.