Triple
T24457696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Subhuman Race |
E616733
|
entity |
| Predicate | hasMoreContemporarySound |
P156184
|
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, hasMoreContemporarySound, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMoreContemporarySound Context triple: [Subhuman Race, hasMoreContemporarySound, true]
-
A.
hasContemporaryInfluences
Indicates that one entity has been shaped, affected, or inspired by other entities from the same or overlapping time period.
-
B.
hasNotableContemporary
Indicates that one entity is recognized as a significant or prominent contemporary (living or active in the same period) of another entity.
-
C.
hasMoreMelodicSoundThan
Indicates that the sound produced by one entity is judged to be more melodic, tuneful, or musically pleasing than the sound produced by another entity.
-
D.
contemporary
Indicates that two entities exist, occur, or are active during the same time period or historical era.
-
E.
hasContemporaryRecognition
Indicates that an entity is currently acknowledged, honored, or widely recognized in the present time or modern era.
- 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_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. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:19 a.m.