Triple
T10109895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | hsn |
E218212
|
entity |
| Predicate | isDialectGroupOf |
P92238
|
FINISHED |
| Object | Chinese |
—
|
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: Chinese | Statement: [hsn, isDialectGroupOf, Chinese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDialectGroupOf Context triple: [hsn, isDialectGroupOf, Chinese]
-
A.
commonInDialectGroup
Indicates that something (such as a word, form, or feature) is frequently used or widely found within a particular dialect group.
-
B.
isBasedOnDialect
Indicates that something (such as a language variety, system, or representation) is derived from, structured around, or primarily influenced by a particular dialect.
-
C.
hasDialectCounterpart
Indicates that one linguistic form or expression has a corresponding equivalent in another dialect.
-
D.
hasDialectsIn
Indicates that a language or linguistic variety possesses distinct dialects that are used or found within a specified region or context.
-
E.
usesDialect
Indicates that one entity communicates or expresses itself using the specific dialect associated with another entity.
- 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_69ca83da93fc8190b54e44bc2b34857c |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd0cdb3c88190a74f75bf865664f3 |
completed | April 2, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9ed7e48190aa132ef8a69b49f9 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4f8f869c8190a82ad040993e0244 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 9:03 p.m.