Triple
T20977107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dark Triad |
E516653
|
entity |
| Predicate | isConceptualizedAs |
P142328
|
FINISHED |
| Object | cluster of overlapping but distinct traits |
—
|
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: cluster of overlapping but distinct traits | Statement: [Dark Triad, isConceptualizedAs, cluster of overlapping but distinct traits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isConceptualizedAs Context triple: [Dark Triad, isConceptualizedAs, cluster of overlapping but distinct traits]
-
A.
conceptualizedFor
Indicates that one entity has been conceived, designed, or mentally framed specifically for use, application, or relevance to another entity.
-
B.
conceptualizedBy
Indicates that something exists as an idea, model, or concept that was formed or defined by a particular agent.
-
C.
isConceptual
Indicates that something exists as an abstract or theoretical idea rather than as a concrete, physical entity.
-
D.
conceptualType
Indicates that one entity represents the conceptual category, class, or abstract type to which another entity belongs.
-
E.
partOfConcept
Indicates that one concept is a constituent or component of a larger, more encompassing concept.
- F. None of above. chosen
Provenance (4 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_69e0b4fee5ac8190875fa9ceba1a5e5e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fba4a0dc819083b90795d26adfff |
completed | April 21, 2026, 4:23 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 1:47 p.m.