Triple
T28495826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elephantulus |
E721103
|
entity |
| Predicate | hasCommonMisconception |
P28207
|
FINISHED |
| Object | thought to be related to shrews due to name |
—
|
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: thought to be related to shrews due to name | Statement: [Elephantulus, hasCommonMisconception, thought to be related to shrews due to name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonMisconception Context triple: [Elephantulus, hasCommonMisconception, thought to be related to shrews due to name]
-
A.
notableMisconception
chosen
Indicates that a commonly held but incorrect belief or understanding exists about the subject.
-
B.
misconceptionSource
Indicates that one entity is the origin or cause from which a particular misconception arises or is derived.
-
C.
misinterpretedBy
Indicates that something (such as a statement, action, or signal) is understood incorrectly or in a way not intended by a particular entity.
-
D.
hasConceptualIssue
Indicates that one entity has a problem, flaw, or inconsistency in its underlying idea, theory, or conceptual basis in relation to another entity.
-
E.
isOftenMisusedBy
Indicates that something is frequently used incorrectly or inappropriately by a particular entity or group.
- 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_69f01a5afdac8190ac6e72d5c100bd58 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69ffb69812808190a751853b30183e65 |
completed | May 9, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69ffb63bdda88190a9dd8426dc0bad43 |
completed | May 9, 2026, 10:33 p.m. |
Created at: April 28, 2026, 3:04 a.m.