Triple
T23759130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jìlǔ Guānhuà |
E587200
|
entity |
| Predicate | isMajorDialectGroupOf |
P92238
|
FINISHED |
| Object | Mandarin 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: Mandarin Chinese | Statement: [Jìlǔ Guānhuà, isMajorDialectGroupOf, Mandarin Chinese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorDialectGroupOf Context triple: [Jìlǔ Guānhuà, isMajorDialectGroupOf, Mandarin Chinese]
-
A.
hasMajorDialectGroup
Indicates that an entity (typically a language) is associated with a primary or major dialect group to which it belongs.
-
B.
isDialectGroupOf
chosen
Indicates that one linguistic variety is a dialect group or cluster belonging to a broader language or language family.
-
C.
isDialectalBaseOf
Indicates that one language variety serves as the primary dialectal source or foundation from which another dialect develops or is derived.
-
D.
isMajorVernacularIn
Indicates that a language is one of the primary commonly spoken languages within a specified region or community.
-
E.
commonInDialectGroup
Indicates that something (such as a word, form, or feature) is frequently used or widely found within a particular dialect group.
- 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_69e2490a0eec81908cdef8a862828d7a |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bdaf52848190b034208de4c4e01a |
completed | April 29, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:14 p.m.