Triple
T21703068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Draco |
E535701
|
entity |
| Predicate | ThubanPoleStarEpoch |
P66369
|
FINISHED |
| Object | around 2700 BCE |
—
|
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: around 2700 BCE | Statement: [Draco, ThubanPoleStarEpoch, around 2700 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ThubanPoleStarEpoch Context triple: [Draco, ThubanPoleStarEpoch, around 2700 BCE]
-
A.
equatorialCoordinateEpoch
chosen
Indicates the specific reference date or epoch at which an object's equatorial coordinates (right ascension and declination) are defined or valid.
-
B.
perihelionYear
Indicates the specific calendar year in which an object's orbit brings it to perihelion, its closest point to the Sun.
-
C.
poleStarOfSouthCelestialPole
Indicates the relationship in which a star serves as the pole star aligned with the south celestial pole.
-
D.
Capella
Indicates a relationship or action involving Capella, whose specific nature depends on the domain or schema in which the predicate is defined.
-
E.
eclipticLongitudeAtDiscovery
Indicates the ecliptic longitude coordinate of an object’s position in the sky at the time it was first discovered.
- 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_69e0c46b44c0819088ab883ebd44e0e8 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef9b8161348190842c433531cfaa5b |
completed | April 27, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69e6969113cc8190ab69855ef5667e4b |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:46 p.m.