Triple
T30867976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | central Hunan |
E786255
|
entity |
| Predicate | languageFamilyOfDialects |
P76528
|
FINISHED |
| Object | Xiang Chinese |
—
|
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: Xiang Chinese | Statement: [central Hunan, languageFamilyOfDialects, Xiang Chinese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageFamilyOfDialects Context triple: [central Hunan, languageFamilyOfDialects, Xiang Chinese]
-
A.
languageFamily
Indicates that two or more languages belong to the same genealogical language family or linguistic lineage.
-
B.
languageFamilyOf
Indicates that one entity is the language family to which the other entity (a specific language) belongs.
-
C.
languageFamilyAssociation
Indicates an association where one entity belongs to, is classified under, or is related to a particular language family.
-
D.
dialectFamily
chosen
Indicates that one dialect belongs to, or is classified under, a particular dialect family.
-
E.
languageIsolateFamily
Indicates that a language belongs to a language family that has no demonstrable genetic relationship to any other known language family.
- 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_69f224b9df2c819086f55f8bcf7f382e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff409ff5548190849c2d50e99bd807 |
completed | May 9, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69ff401a5e188190a72f945e910b4a6c |
completed | May 9, 2026, 2:09 p.m. |
Created at: April 29, 2026, 8:47 p.m.