Triple
T30028171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oh My God |
E762936
|
entity |
| Predicate | hasEuphemisticForm |
P75881
|
FINISHED |
| Object | Oh my gosh |
—
|
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: Oh my gosh | Statement: [Oh My God, hasEuphemisticForm, Oh my gosh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEuphemisticForm Context triple: [Oh My God, hasEuphemisticForm, Oh my gosh]
-
A.
euphemisticReferenceTo
chosen
Indicates that one expression is used as a milder or less direct way of referring to another, often to soften or obscure its impact.
-
B.
hasMetaphoricalForm
Indicates that one entity is expressed, represented, or understood through a metaphorical form or figurative expression involving another entity.
-
C.
hasLenitedForm
Indicates that one form of a word is the lenited (softened or mutated) version of another form.
-
D.
hasApologeticFunction
Indicates that something serves the role of expressing regret, remorse, or an apology in a given context.
-
E.
hasAdjectiveForm
Indicates that one term is the adjective form derived from another related term (such as a noun or verb).
- 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.