Triple
T33975911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noriko |
E871137
|
entity |
| Predicate | startsWithConsonant |
P201476
|
FINISHED |
| Object | N |
—
|
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: N | Statement: [Noriko, startsWithConsonant, N]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startsWithConsonant Context triple: [Noriko, startsWithConsonant, N]
-
A.
usesConsonantInitials
Indicates that an entity’s initials or abbreviated form begin with consonant letters rather than vowels.
-
B.
hasClickConsonants
Indicates that the subject language includes click consonant sounds in its phonemic inventory.
-
C.
isConsonant
Indicates that a given character or sound is a consonant rather than a vowel or other symbol.
-
D.
hasNumberOfConsonantLetters
Indicates the relationship between an entity and the count of consonant letters present in its written form.
-
E.
hasConsonantPhonemes
Indicates that an entity possesses or includes one or more consonant phonemes in its phonological system.
- F. None of above. chosen
Provenance (4 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_69f3499da0188190ab1a4ff06fb06a2a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fff9b126b4819085a4cf8791d388d1 |
completed | May 10, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69fff8f913a881908d3b7e490d92631f |
completed | May 10, 2026, 3:18 a.m. |
| PDg | Predicate description generation | batch_69fff9b0338c8190a24ed0b5dc9784b2 |
completed | May 10, 2026, 3:21 a.m. |
Created at: May 1, 2026, 1:50 a.m.