Triple
T4217548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baade’s star |
E94255
|
entity |
| Predicate | epochOfKeyObservations |
P55369
|
FINISHED |
| Object | mid-20th century |
—
|
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: mid-20th century | Statement: [Baade’s star, epochOfKeyObservations, mid-20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: epochOfKeyObservations Context triple: [Baade’s star, epochOfKeyObservations, mid-20th century]
-
A.
epochReference
Indicates a temporal relationship where one time expression is interpreted relative to a specified reference epoch or baseline time.
-
B.
keyObservation
Indicates that an entity is a primary or crucial observation about another entity, typically highlighting a central finding, feature, or insight.
-
C.
sectorObservationTime
Indicates the specific time at which an observation related to a particular sector is made or recorded.
-
D.
observedSince
Indicates that one entity has been continuously or repeatedly observed starting from a specified point in time.
-
E.
calendarEpoch
Indicates the reference starting point in time from which a particular calendar system counts its dates.
- 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_69b3451997e08190851db4a9a588837d |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b34e4bf6088190926b982039a12079 |
completed | March 12, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69b347f1d7b48190bd8974c03c7dc937 |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e4ace648190acf911853d4fcf86 |
completed | March 12, 2026, 11:37 p.m. |
Created at: March 12, 2026, 11:04 p.m.