Triple
T30028166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oh My God |
E762936
|
entity |
| Predicate | prosody |
P62940
|
FINISHED |
| Object | often stressed for emphasis |
—
|
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: often stressed for emphasis | Statement: [Oh My God, prosody, often stressed for emphasis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prosody Context triple: [Oh My God, prosody, often stressed for emphasis]
-
A.
hasProsodicType
chosen
Indicates that one entity is characterized by a particular prosodic pattern or category (such as stress, intonation, or rhythm type) in relation to another.
-
B.
hasProsodicUnit
Indicates that one element contains, corresponds to, or is associated with a specific prosodic unit (such as a syllable, foot, or intonational phrase) in the prosodic structure.
-
C.
tone
Indicates the characteristic attitude or emotional quality expressed in how something is communicated or presented.
-
D.
vocalization
Indicates the act or manner of producing sounds or calls, typically as a means of communication.
-
E.
vocalizationCharacteristic
Indicates how an entity’s vocal sounds are characterized, such as their quality, style, or distinctive acoustic features.
- 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_69f2246ee6e48190b69e837b913b398a |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f679ad19f88190a01d97605aecb0d8 |
completed | May 2, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:49 p.m.