Triple
T22912306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reciprocal Recording |
E568632
|
entity |
| Predicate | knownForSound |
P88335
|
FINISHED |
| Object | raw grunge sound |
—
|
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: raw grunge sound | Statement: [Reciprocal Recording, knownForSound, raw grunge sound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownForSound Context triple: [Reciprocal Recording, knownForSound, raw grunge sound]
-
A.
knownForAct
Indicates that an entity is recognized or notable for performing a particular act or action.
-
B.
namedForKnownFor
Indicates that one entity is named after another entity specifically because that other entity is notable or recognized for something.
-
C.
nowKnownFor
Indicates that an entity is currently recognized or notable for a particular role, attribute, achievement, or association.
-
D.
knownForGenre
chosen
Indicates that an entity is recognized or notable for working in, producing, or being associated with a particular genre.
-
E.
knownForRoleIn
Indicates that an entity is recognized or notable for performing a particular role in a specific work, project, or context.
- 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_69e2458d90c88190a58cead4e781ca6a |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18075a0048190bd150e2badeeb7c2 |
completed | April 29, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:42 p.m.