Triple
T7572516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regulidae |
E179277
|
entity |
| Predicate | typeGenus |
P5980
|
FINISHED |
| Object | Regulus |
E673767
|
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: [Regulidae, typeGenus, Regulus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Regulus Context triple: [Regulidae, typeGenus, 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
chosen
Regulus is a genus of very small, active songbirds commonly known as kinglets, found across the Northern Hemisphere.
-
C.
Aldebaran
Aldebaran is a bright orange giant star in the constellation Taurus, known as one of the most prominent stars in the night sky.
-
D.
Sirius
Sirius is the brightest star in the night sky, a nearby binary star system in the constellation Canis Major that has featured prominently in astronomy, mythology, and literature.
-
E.
Denebola
Denebola is a bright white main-sequence star in the constellation Leo, notable as one of its primary corner stars and for possessing a surrounding debris disk.
- 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_69c69f316e50819081a271c85c06f918 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f94710a0819094508356b8d610ab |
completed | March 27, 2026, 9:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8616207f88190834dc2412001af3f |
completed | March 28, 2026, 11:16 p.m. |
Created at: March 27, 2026, 3:51 p.m.