Triple
T8717241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dorado |
E206925
|
entity |
| Predicate | borders |
P224
|
FINISHED |
| Object | Horologium |
E481646
|
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: Horologium | Statement: [Dorado, borders, Horologium]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Horologium Context triple: [Dorado, borders, Horologium]
-
A.
Horologium
chosen
Horologium is a faint southern constellation named after a pendulum clock, introduced in the 18th century by French astronomer Nicolas-Louis de Lacaille.
-
B.
Orrery
An orrery is a mechanical model of the solar system that illustrates the relative motions of the planets and moons around the Sun.
-
C.
Reticulum
Reticulum is a small, faint southern constellation named after a reticle or net, located near the Large Magellanic Cloud.
-
D.
Coma Berenices
Coma Berenices is a small northern constellation notable for its rich star fields and prominent galaxy clusters, located between Leo and Boötes.
-
E.
Telescopium
Telescopium is a small, faint southern constellation introduced in the 18th century and named after the telescope.
- 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_69ca83572d4881909bef3be2b578d539 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5cd9c2a08190a65ab0ce573153d2 |
completed | March 31, 2026, 11:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf28df657881908c1fc67c2c777cea |
completed | April 3, 2026, 2:41 a.m. |
Created at: March 30, 2026, 6:36 p.m.