Triple
T19950903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dent marble |
E479549
|
entity |
| Predicate | isMisnomer |
P41085
|
FINISHED |
| Object | not a true geological marble |
—
|
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: not a true geological marble | Statement: [Dent marble, isMisnomer, not a true geological marble]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMisnomer Context triple: [Dent marble, isMisnomer, not a true geological marble]
-
A.
misinterpretedBy
Indicates that something (such as a statement, action, or signal) is understood incorrectly or in a way not intended by a particular entity.
-
B.
misrepresentedAs
chosen
Indicates that one entity is falsely or inaccurately presented, portrayed, or described as another entity or in another way.
-
C.
misidentifiedAs
Indicates that one entity has been incorrectly recognized, labeled, or understood as another, distinct entity.
-
D.
misappliedAs
Indicates that something has been used, interpreted, or assigned in an incorrect, inappropriate, or unintended way.
-
E.
notableMisconception
Indicates that a commonly held but incorrect belief or understanding exists about the subject.
- 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a6b694c819080daea9422bcdd38 |
completed | April 20, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69e537f47c508190853c4e009c6b5566 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.