Triple
T15260517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eclipse |
E364761
|
entity |
| Predicate | damsire |
P56417
|
FINISHED |
| Object | Regulus |
E1147045
|
NE 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: Regulus | Statement: [Eclipse, damsire, Regulus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Regulus Context triple: [Eclipse, damsire, Regulus]
-
A.
Regulus
Regulus is the brightest star in the constellation Leo, a hot blue-white multiple star system located relatively close to Earth.
-
B.
Regulus
Regulus is a genus of very small, active songbirds commonly known as kinglets, found across the Northern Hemisphere.
-
C.
Regulus
Regulus is an ancient Roman cognomen most famously associated with several notable statesmen and generals of the Roman Republic and early Empire.
-
D.
Regulus
chosen
Regulus was an 18th-century British Thoroughbred racehorse and influential sire, renowned for his undefeated racing career and lasting impact on bloodlines.
-
E.
Aldebaran
Aldebaran is a bright orange giant star in the constellation Taurus, known as one of the most prominent stars in the night sky.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0084e85a08190b8e63598b9f6a535 |
completed | April 15, 2026, 9:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69feef6def4c8190b6aed1f68d336c5a |
completed | May 9, 2026, 8:25 a.m. |
Created at: April 10, 2026, 3:14 a.m.