Triple
T24457697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Subhuman Race |
E616733
|
entity |
| Predicate | incorporatesModernMetalElements |
P136357
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Subhuman Race, incorporatesModernMetalElements, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incorporatesModernMetalElements Context triple: [Subhuman Race, incorporatesModernMetalElements, true]
-
A.
incorporatesMetalInfluence
chosen
Indicates that something includes or integrates stylistic, structural, or thematic elements characteristic of metal (e.g., metal music or metal aesthetics) into its overall composition or design.
-
B.
stateMetal
Indicates that an entity is in a metallic state or exhibits properties characteristic of a metal.
-
C.
metalCore
Indicates that one entity serves as the central metallic component or core material of another entity.
-
D.
allMetalConstruction
Indicates that something is constructed entirely or almost entirely from metal components.
-
E.
associatedMetal
Indicates a relationship where one entity is linked or connected to a particular metal, such as by composition, usage, origin, or symbolic association.
- 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_69e2d7ef9fe08190a0613908758b4e86 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f298c812bc8190969836ee8f0eb2f2 |
completed | April 29, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:19 a.m.