Triple
T10583016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nox |
E249781
|
entity |
| Predicate | parentOf |
P120
|
FINISHED |
| Object | Mors |
E873104
|
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: Mors | Statement: [Nox, parentOf, Mors]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mors Context triple: [Nox, parentOf, Mors]
-
A.
Mors
Mors is a large Danish island in the Limfjord, known for its varied coastal landscapes, agricultural areas, and the town of Nykøbing Mors.
-
B.
Mors
chosen
Mors is the Roman personification of death, often depicted as a shadowy or skeletal figure associated with the end of life.
-
C.
Morsum
Morsum is a village on the German North Sea island of Sylt, known for its traditional thatched-roof houses and the nearby Morsum Cliff nature reserve.
-
D.
Mór
Mór is a town in central Hungary known for its wine production and location between the Vértes and Bakony hills.
-
E.
Mure
Mure is a Scottish surname historically associated with Lowland families and often considered a variant of or related to the name Muir.
- 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d52766d53c8190b51753768ab58c31 |
completed | April 7, 2026, 3:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d95e7df88081908e3d77f357f176e3 |
completed | April 10, 2026, 8:33 p.m. |
Created at: April 6, 2026, 12:39 p.m.