Triple
T5775469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monoceros |
E127429
|
entity |
| Predicate | borders |
P224
|
FINISHED |
| Object | Lepus |
E126209
|
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: Lepus | Statement: [Monoceros, borders, Lepus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lepus Context triple: [Monoceros, borders, Lepus]
-
A.
Lepus
chosen
Lepus is a small southern constellation located just below Orion, traditionally representing a hare.
-
B.
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.
-
C.
Moschus
Moschus is a genus of small, fanged musk deer native to Asia, known for the males’ musk glands historically prized in perfumery and traditional medicine.
-
D.
Volpe
Volpe is an Italian surname borne by various notable individuals in politics, sports, and the arts.
-
E.
Cercaphus
Cercaphus is a figure from Greek mythology known primarily as a descendant of the nymph Rhode and a member of the early mythic rulers associated with the island of Rhodes.
- 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_69c008361fa88190aefa4dc41b051e7f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029de3bb4819087a6f3e920e12990 |
completed | March 22, 2026, 5:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c1134155608190bc9271dba417a512 |
completed | March 23, 2026, 10:17 a.m. |
Created at: March 22, 2026, 3:50 p.m.