Triple
T9515116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | star catalogue of the southern hemisphere (1679–1678 observations) |
E229504
|
entity |
| Predicate | observationStart |
P3267
|
FINISHED |
| Object | 1677 |
—
|
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: 1677 | Statement: [star catalogue of the southern hemisphere (1679–1678 observations), observationStart, 1677]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observationStart Context triple: [star catalogue of the southern hemisphere (1679–1678 observations), observationStart, 1677]
-
A.
observationType
Indicates the specific kind or category of observation being made or recorded in a given context.
-
B.
observation
Indicates that one entity perceives, monitors, or takes note of another entity or phenomenon, typically to gather information about it.
-
C.
instructionBegan
Indicates that an instructional process or teaching activity has started.
-
D.
operationStart
chosen
Indicates the point in time or event at which a specific operation or process begins.
-
E.
observedFor
Indicates that one entity is monitored, watched, or examined over a period of time for the benefit or analysis of another entity.
- 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_69ca84777560819084cddd999badc1aa |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd986d5af08190a001c5a5ff647d4d |
completed | April 1, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cca56a3d088190bdc16670678fb6c6 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:58 p.m.