Triple
T19261102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caelum |
E481650
|
entity |
| Predicate | borderingConstellation |
P224
|
FINISHED |
| Object | Lepus |
—
|
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: Lepus | Statement: [Caelum, borderingConstellation, Lepus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lepus Context triple: [Caelum, borderingConstellation, Lepus]
-
A.
Lepus
Lepus is a genus of fast-running mammals commonly known as hares and jackrabbits, found across much of the world in open and semi-open habitats.
-
B.
Lepus
chosen
Lepus is a small southern constellation located just below Orion, traditionally representing a hare.
-
C.
Lapine
Lapine is a surname most notably associated with American theater director and playwright James Lapine, known for his collaborations with composer Stephen Sondheim.
-
D.
Lepus victoriae
Lepus victoriae, commonly known as the African savanna hare, is a species of hare native to sub-Saharan Africa, typically inhabiting open grasslands and savannas.
-
E.
Lepus peguensis
Lepus peguensis, commonly known as the Burmese hare, is a species of hare native to parts of Southeast Asia, particularly Myanmar and surrounding regions.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb890e7c8190beba407f63459382 |
completed | April 20, 2026, 10:10 a.m. |
Created at: April 10, 2026, 1:28 p.m.