Triple
T23185911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Besselian year |
E579592
|
entity |
| Predicate | typicalEpochExamples |
P146566
|
FINISHED |
| Object | B1900.0 |
—
|
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: B1900.0 | Statement: [Besselian year, typicalEpochExamples, B1900.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEpochExamples Context triple: [Besselian year, typicalEpochExamples, B1900.0]
-
A.
DecEpoch
Indicates the specific point in time (epoch) at which a declination (Dec) measurement or coordinate value is defined or referenced.
-
B.
mappingEpoch
chosen
Indicates the specific time period or version during which a particular mapping or correspondence between entities is defined or valid.
-
C.
epochReference
Indicates a temporal relationship where one time expression is interpreted relative to a specified reference epoch or baseline time.
-
D.
recurringEra
Indicates a relationship where a particular era or time period repeats or recurs, rather than occurring only once.
-
E.
RAEpoch
Indicates the specific epoch or time period during which a right ascension (RA) value is defined or measured.
- 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_69e245ff8000819090d12008805315b7 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18fd3aaa08190b9cf7afe4ee5a38d |
completed | April 29, 2026, 4:57 a.m. |
| PD | Predicate disambiguation | batch_69ef8a041c0081909afb670d17a5aaba |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:05 p.m.