Triple
T20326808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RR Lyrae variable star |
E492359
|
entity |
| Predicate | typicalPeriodRange |
P139699
|
FINISHED |
| Object | 0.2 to 1 day |
—
|
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.2 to 1 day | Statement: [RR Lyrae variable star, typicalPeriodRange, 0.2 to 1 day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPeriodRange Context triple: [RR Lyrae variable star, typicalPeriodRange, 0.2 to 1 day]
-
A.
typicalPeriod
Indicates the usual or characteristic time interval or duration associated with an event, process, or state.
-
B.
typicalEndDateRange
Indicates the usual or expected range of end dates associated with an event, activity, or time-bounded entity.
-
C.
establishedPeriod
Indicates the time span or date range during which something was founded, created, or formally brought into existence.
-
D.
typicalStartPeriod
Indicates the usual or standard time period during which something begins or is initiated.
-
E.
typicalCollectionPeriodStart
Indicates the date or point in time when a standard or customary collection period begins.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e677e4130081909ec54f131939e442 |
completed | April 20, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:21 a.m.