Triple
T19558584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delta Scuti |
E489380
|
entity |
| Predicate | pulsationPeriod_days |
P135595
|
FINISHED |
| Object | ~0.1938 |
—
|
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.1938 | Statement: [Delta Scuti, pulsationPeriod_days, ~0.1938]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pulsationPeriod_days Context triple: [Delta Scuti, pulsationPeriod_days, ~0.1938]
-
A.
meanPulsationPeriod_days
chosen
Indicates the average duration, measured in days, of a repeating pulsation cycle for the entity in question.
-
B.
pulsarSpinPeriod
Indicates the duration of one complete rotation of a pulsar, expressing how long it takes the pulsar to spin once about its axis.
-
C.
synodicPeriod_days
Indicates the length of time, measured in days, between successive identical configurations (e.g., conjunctions or oppositions) of two orbiting bodies as seen from a given reference point.
-
D.
pulsationMechanism
Indicates the physical process or mechanism responsible for producing and sustaining a periodic pulsation in an object or system.
-
E.
hasRotationPeriod
Indicates that one entity has a specified duration for completing a full rotation around its own axis.
- 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_69d8e8dc5d8c8190a6d7bd8864f43ca0 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63f723d5081909553a4363b579a6b |
completed | April 20, 2026, 3 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:42 p.m.