Triple
T31214481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stranger in Moscow |
E795833
|
entity |
| Predicate | featuresSpokenOutro |
P111474
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Stranger in Moscow, featuresSpokenOutro, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresSpokenOutro Context triple: [Stranger in Moscow, featuresSpokenOutro, yes]
-
A.
featuresSpokenVerses
Indicates that something includes or presents spoken verses as a notable component or element.
-
B.
featuresMonologues
chosen
Indicates that something (such as a work, performance, or medium) contains or includes one or more monologues as a notable element.
-
C.
featuresSpokenOrChildVocal
Indicates that the subject has characteristics related to spoken language or vocalizations produced by a child.
-
D.
speakerFeatures
Indicates that certain characteristics, attributes, or properties are associated with a speaker in a given context.
-
E.
featuresInstrumentalDialogue
Indicates that the situation or work includes dialogue that serves an instrumental or functional purpose, such as advancing a task, plan, or procedure.
- 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_6a0062e6bd788190a7b4f3e5befb5cbb |
completed | May 10, 2026, 10:50 a.m. |
| PD | Predicate disambiguation | batch_6a0061989d188190b4815b2de3e8676f |
completed | May 10, 2026, 10:44 a.m. |
Created at: April 29, 2026, 9:10 p.m.