Triple
T8880909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhaotong |
E211406
|
entity |
| Predicate | hasRegionalAlias |
P40944
|
FINISHED |
| Object | gateway to northeastern Yunnan |
—
|
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: gateway to northeastern Yunnan | Statement: [Zhaotong, hasRegionalAlias, gateway to northeastern Yunnan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionalAlias Context triple: [Zhaotong, hasRegionalAlias, gateway to northeastern Yunnan]
-
A.
hasRegionalName
chosen
Indicates that an entity is known by a specific name or designation within a particular region or locality.
-
B.
hasAbbreviationForRegion
Indicates that one entity is used as the standard abbreviated form of the name of a particular region.
-
C.
isRegionalAlternativeTo
Indicates that one entity serves as a counterpart or substitute for another within a specific geographic region or local context.
-
D.
hasRegionalIdentity
Indicates that an entity possesses or is associated with a specific regional or local identity.
-
E.
hasRegionalVariationsIn
Indicates that something exhibits different forms, versions, or characteristics depending on the geographic region.
- 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_69ca838f9e20819096ab1f236a70381a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6168e3d881908c58cf11cf5f9a0e |
completed | April 1, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2956788190a311c647b4da17a6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:52 p.m.