Triple
T21818809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beta Cephei |
E538669
|
entity |
| Predicate | hasPulsationPeriodRange |
P135595
|
FINISHED |
| Object | 0.1–0.6 days |
—
|
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: 0.1–0.6 days | Statement: [Beta Cephei, hasPulsationPeriodRange, 0.1–0.6 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPulsationPeriodRange Context triple: [Beta Cephei, hasPulsationPeriodRange, 0.1–0.6 days]
-
A.
hasPulsations
Indicates that an entity exhibits rhythmic, repeated pulsating behavior or variations over time.
-
B.
pulsationPeriod_hours
Indicates the duration, measured in hours, of one complete pulsation cycle of an object or system.
-
C.
pulsePeriodStability
Indicates how consistently the time interval between successive pulses remains the same over repeated measurements.
-
D.
meanPulsationPeriod_days
chosen
Indicates the average duration, measured in days, of a repeating pulsation cycle for the entity in question.
-
E.
hasPeriodRange
Indicates that there is a temporal span or interval during which something is valid, active, or applicable.
- 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_69e0c475038c8190abb9b1a20eb8ff50 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f07ccd0d908190a43af4fcc7d6ca03 |
completed | April 28, 2026, 9:24 a.m. |
| PD | Predicate disambiguation | batch_69e6be815a108190be81d7c987d0c0d6 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:54 p.m.