Triple
T8949574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shíyàn |
E213309
|
entity |
| Predicate | secondSyllableTone |
P86505
|
FINISHED |
| Object | fourth 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: fourth tone | Statement: [Shíyàn, secondSyllableTone, fourth tone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondSyllableTone Context triple: [Shíyàn, secondSyllableTone, fourth tone]
-
A.
secondaryTone
Indicates that one tone functions as a secondary or supporting tonal element in relation to a primary tone within a given context.
-
B.
secondLetter
Indicates that one entity is the second letter (in sequence or position) of another entity, typically a string or word.
-
C.
tonalityOfSecondMovement
Indicates the key or tonal center that characterizes the second movement of a musical work.
-
D.
secondElement
Indicates that one entity is the second element in an ordered pair, sequence, or collection relative to another entity.
-
E.
secondWord
Indicates that one entity is the second word in sequence immediately following the first entity in a text or utterance.
- 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_69ca839843408190a39069a029a89f15 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc670b5f50819080f1c73992fe5281 |
completed | April 1, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed5267c8190a43feb2a2f3df1ec |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc60e0d7208190966797ce5f95fe49 |
completed | April 1, 2026, 12:03 a.m. |
Created at: March 30, 2026, 6:59 p.m.