Triple
T2562617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mandarin phonology |
E57275
|
entity |
| Predicate | includesTone |
P12025
|
FINISHED |
| Object | high-level tone |
—
|
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: high-level tone | Statement: [Mandarin phonology, includesTone, high-level tone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesTone Context triple: [Mandarin phonology, includesTone, high-level tone]
-
A.
hasPhonemicTone
chosen
Indicates that a language, word, or syllable uses pitch differences (tones) as phonemic contrasts that can change meaning.
-
B.
tone
Indicates the characteristic attitude or emotional quality expressed in how something is communicated or presented.
-
C.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
-
D.
includesSaying
Indicates that one entity (such as a text, speech, or communication) contains or incorporates a particular saying, phrase, or quoted expression.
-
E.
hasHeavierSoundThan
Indicates that one entity produces or is associated with a sound that is sonically heavier, more intense, or more forceful than that of another entity.
- 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_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. |
Created at: March 6, 2026, 9:48 p.m.