Triple
T24457675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Subhuman Race |
E616733
|
entity |
| Predicate | hasMoreAggressiveSound |
P22072
|
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, hasMoreAggressiveSound, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMoreAggressiveSound Context triple: [Subhuman Race, hasMoreAggressiveSound, true]
-
A.
hasHeavierSoundThan
chosen
Indicates that one entity produces or is associated with a sound that is sonically heavier, more intense, or more forceful than that of another entity.
-
B.
hasStrongerAcousticSound
Indicates that one entity produces a louder or more intense acoustic sound than another entity.
-
C.
hasSound
Indicates that an entity produces, emits, or is associated with a particular sound.
-
D.
hasCatchySound
Indicates that something possesses an appealing, memorable, or attractive auditory quality.
-
E.
hasMatureSound
Indicates that an entity produces or is associated with a sound quality characteristic of adulthood or full development, as opposed to a youthful or immature sound.
- 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.