Triple
T22999123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regulus |
E572586
|
entity |
| Predicate | hasComponent |
P35
|
FINISHED |
| Object | Regulus C |
—
|
NE NERFINISHED |
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 C | Statement: [Regulus, hasComponent, Regulus C]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Regulus C Context triple: [Regulus, hasComponent, Regulus C]
-
A.
St Regulus
St Regulus is a legendary early Christian figure traditionally associated with bringing the relics of Saint Andrew to Scotland, particularly to the site of modern St Andrews.
-
B.
Regulus
Regulus is a given name most notably associated with Regulus Arcturus Black, a character from the Harry Potter series.
-
C.
Regulus
chosen
Regulus is the brightest star in the constellation Leo, a hot blue-white multiple star system located relatively close to Earth.
-
D.
Regulus
Regulus is a genus of very small, active songbirds commonly known as kinglets, found across the Northern Hemisphere.
-
E.
Regulus
Regulus was an 18th-century British Thoroughbred racehorse and influential sire, renowned for his undefeated racing career and lasting impact on bloodlines.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182f54ce88190930530958e2a1830 |
completed | April 29, 2026, 4:03 a.m. |
Created at: April 17, 2026, 3:50 p.m.