Triple
T22431989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guangdong Romanization |
E554522
|
entity |
| Predicate | representsInitialConsonants |
P23485
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Guangdong Romanization, representsInitialConsonants, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsInitialConsonants Context triple: [Guangdong Romanization, representsInitialConsonants, true]
-
A.
usesConsonantInitials
Indicates that an entity’s initials or abbreviated form begin with consonant letters rather than vowels.
-
B.
hasConsonantClustersRepresentation
chosen
Indicates that there is a representation capturing how consonant clusters are structured or realized in a given form or system.
-
C.
representsVowels
Indicates that an entity functions as or stands for vowel characters within a given context or system.
-
D.
representsSemivowel
Indicates that one entity functions as or is classified as a semivowel in relation to another entity.
-
E.
hasConsonantClasses
Indicates that an entity (typically a language or phonological system) possesses a defined set or system of consonant classes.
- 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_69e11e5010e48190ae1e9c9db9697637 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15a32139481909baaf9275f5e0257 |
completed | April 29, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.