Triple
T1258451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taurus |
E12444
|
entity |
| Predicate | startDateSidereal |
P26311
|
FINISHED |
| Object | approximately May 14 |
—
|
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: approximately May 14 | Statement: [Taurus, startDateSidereal, approximately May 14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startDateSidereal Context triple: [Taurus, startDateSidereal, approximately May 14]
-
A.
rightAscension
Indicates the angular distance of an object measured eastward along the celestial equator from the vernal equinox, specifying its position in the sky.
-
B.
solarAlignmentDates
Indicates the specific dates on which an object, structure, or location is aligned in a significant way with the position of the Sun (e.g., sunrise, sunset, solstices, or equinoxes).
-
C.
celestialLocation
Indicates the spatial or positional relationship of an entity relative to a celestial body or region in space.
-
D.
rightAscensionRange
Indicates that an entity’s right ascension lies within a specified angular interval on the celestial sphere.
-
E.
orbitFirstReachedDate
Indicates the date on which an object first successfully entered and achieved its intended orbit.
- 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_69a4933352e08190ac617291985e76c0 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bfaa2b508190a3f61c67b3fa3ad4 |
completed | March 1, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6eefbc81908dddd7d2ef368186 |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bd98b62c8190a5f6710345c0537d |
completed | March 1, 2026, 10:28 p.m. |
Created at: March 1, 2026, 7:50 p.m.