Triple
T31214482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stranger in Moscow |
E795833
|
entity |
| Predicate | containsSoundEffect |
P124232
|
FINISHED |
| Object | rain |
—
|
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: rain | Statement: [Stranger in Moscow, containsSoundEffect, rain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsSoundEffect Context triple: [Stranger in Moscow, containsSoundEffect, rain]
-
A.
containsSound
chosen
Indicates that one entity includes, embodies, or produces the sound associated with another entity.
-
B.
hasSound
Indicates that an entity produces, emits, or is associated with a particular sound.
-
C.
usesSound
Indicates that one entity employs or relies on sound as a means or tool in relation to another entity or context.
-
D.
hasSoundEngine
Indicates that one entity is equipped with or contains a sound engine component.
-
E.
hasPartialSound
Indicates that one entity’s sound is included as a component or segment within the sound of another entity.
- 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff6074bcd4819090b72cd6209ff206 |
completed | May 9, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69ff600aba888190812a6e7eca0283b8 |
completed | May 9, 2026, 4:25 p.m. |
Created at: April 29, 2026, 9:10 p.m.