Triple
T30028160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oh My God |
E762936
|
entity |
| Predicate | capitalizationVariant |
P12011
|
FINISHED |
| Object | oh my God |
—
|
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 God | Statement: [Oh My God, capitalizationVariant, oh my God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalizationVariant Context triple: [Oh My God, capitalizationVariant, oh my God]
-
A.
capitalizationPolicy
Indicates the rules or conventions governing how letters are capitalized in a given context (e.g., text, names, or identifiers).
-
B.
preferredCapitalization
Indicates the specific way a term’s letters should be capitalized when it is written or displayed.
-
C.
usesCapitalization
Indicates that one entity applies specific capitalization (such as upper/lower case or title case) to another entity, typically a string or text element.
-
D.
caseSensitivityVariant
chosen
Indicates that one string or textual form is a variant of another that differs only in letter casing (e.g., uppercase vs lowercase).
-
E.
capitalizationEffect
Indicates how the use of uppercase and lowercase letters in a word or text influences its interpretation, appearance, or impact.
- 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_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: April 29, 2026, 6:49 p.m.