Triple
T2562627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mandarin phonology |
E57275
|
entity |
| Predicate | hasConsonantPlace |
P40500
|
FINISHED |
| Object | bilabial |
—
|
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: bilabial | Statement: [Mandarin phonology, hasConsonantPlace, bilabial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConsonantPlace Context triple: [Mandarin phonology, hasConsonantPlace, bilabial]
-
A.
hasConsonantPhonemes
Indicates that an entity possesses or includes one or more consonant phonemes in its phonological system.
-
B.
hasConsonantClusters
Indicates that the subject contains sequences of two or more consonants occurring together without intervening vowels.
-
C.
hasConsonantSigns
Indicates that one entity possesses or includes consonant sign characters as part of its representation or structure.
-
D.
hasClickConsonants
Indicates that the subject language includes click consonant sounds in its phonemic inventory.
-
E.
hasConsonantGradation
Indicates that a word undergoes systematic alternation of its consonants (consonant gradation) in different morphological or phonological forms.
- 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_69ab4a4ef9008190a0e6d4422b9418b7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd35c6ee88190b6eaa1841d3e99a4 |
completed | March 7, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69abd0caeb488190b0dd8e48d0f2777d |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd35b216881908f4ef32d1c1e5080 |
completed | March 7, 2026, 7:27 a.m. |
Created at: March 6, 2026, 9:48 p.m.