Triple
T18552040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B Cassiopeiae |
E453400
|
entity |
| Predicate | peakVisibilityDateRange |
P79697
|
FINISHED |
| Object | late 1572 to early 1573 |
—
|
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: late 1572 to early 1573 | Statement: [B Cassiopeiae, peakVisibilityDateRange, late 1572 to early 1573]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakVisibilityDateRange Context triple: [B Cassiopeiae, peakVisibilityDateRange, late 1572 to early 1573]
-
A.
peakVisibility
Indicates the degree to which a peak (such as a mountain or summit) is visible from a given location or under certain conditions.
-
B.
peakExportPeriod
Indicates the time period during which exports of a given item or from a given source reach their highest level.
-
C.
showsTimePeriod
chosen
Indicates that one entity presents or displays a specific span or interval of time associated with another entity.
-
D.
typicalEndDateRange
Indicates the usual or expected range of end dates associated with an event, activity, or time-bounded entity.
-
E.
peakDays
Indicates the days on which something reaches its highest or most intense level of activity, usage, or occurrence.
- 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_69d8d388b0c881908e610a1c45b52640 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e538019a74819099dbd255fb21fa95 |
completed | April 19, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:38 a.m.