Triple
T29008047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mus musculus castaneus |
E736488
|
entity |
| Predicate | hasMitochondrialLineage |
P159334
|
FINISHED |
| Object | distinct from Mus musculus domesticus |
—
|
LITERAL 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: distinct from Mus musculus domesticus | Statement: [Mus musculus castaneus, hasMitochondrialLineage, distinct from Mus musculus domesticus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMitochondrialLineage Context triple: [Mus musculus castaneus, hasMitochondrialLineage, distinct from Mus musculus domesticus]
-
A.
hasPatrilinealOrigin
Indicates that something originates from or is derived through the male (father’s) ancestral line.
-
B.
hasMitosomes
Indicates that an organism or cell possesses mitosomes as part of its cellular structure.
-
C.
mtHaplogroup
chosen
Indicates that one entity is classified as having a specific mitochondrial DNA haplogroup associated with the other entity.
-
D.
hasNotableLineageFor
Indicates that one entity possesses a distinguished or noteworthy ancestry, heritage, or lineage in relation to another entity.
-
E.
hasAncestralRoots
Indicates that one entity originates from, descends from, or is historically rooted in another entity or place.
- F. None of above.
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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 28, 2026, 9:39 a.m.