Triple
T15793856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garry |
E382924
|
entity |
| Predicate | hasTwoConsonantSpelling |
P33543
|
FINISHED |
| Object | "rr" in the middle |
—
|
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: "rr" in the middle | Statement: [Garry, hasTwoConsonantSpelling, "rr" in the middle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTwoConsonantSpelling Context triple: [Garry, hasTwoConsonantSpelling, "rr" in the middle]
-
A.
hasConsonantClusters
chosen
Indicates that the subject contains sequences of two or more consonants occurring together without intervening vowels.
-
B.
hasConsonantPhonemes
Indicates that an entity possesses or includes one or more consonant phonemes in its phonological system.
-
C.
hasNumberOfConsonantLetters
Indicates the relationship between an entity and the count of consonant letters present in its written form.
-
D.
hasConsonantVowelStructure
Indicates that something (typically a word or syllable) follows a specific pattern or arrangement of consonant and vowel sounds.
-
E.
usesConsonantInitials
Indicates that an entity’s initials or abbreviated form begin with consonant letters rather than vowels.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4db55308190875a04f982c44cea |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e00537bd1c81908d6e832792fd934f |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:48 a.m.