Triple
T27871709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xiong |
E704506
|
entity |
| Predicate | hasPronunciationSystem |
P41705
|
FINISHED |
| Object | Hanyu Pinyin |
—
|
NE NERFINISHED |
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: Hanyu Pinyin | Statement: [Xiong, hasPronunciationSystem, Hanyu Pinyin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPronunciationSystem Context triple: [Xiong, hasPronunciationSystem, Hanyu Pinyin]
-
A.
hasPronunciationInformation
Indicates that there is available information describing how something is pronounced.
-
B.
usesPhoneticSystem
chosen
Indicates that one entity employs or is based on a particular phonetic system for representing or encoding sounds.
-
C.
hasStandardPronunciationBasedOn
Indicates that one entity’s standard or canonical pronunciation is determined or derived from another entity’s pronunciation.
-
D.
hasPronunciationDifferenceFrom
Indicates that two linguistic items differ in how they are pronounced.
-
E.
hasPhonologicalStandard
Indicates that one entity serves as the accepted or prescribed phonological norm or standard for the pronunciation system 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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fe6fea4a288190bf8615c5d6bf41b4 |
completed | May 8, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69fe6f774de08190975a2393b9a1fd22 |
completed | May 8, 2026, 11:19 p.m. |
Created at: April 27, 2026, 6:24 p.m.