Triple
T28759526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guan |
E731769
|
entity |
| Predicate | hasNotableVariantUsageRegion |
P92260
|
FINISHED |
| Object | Cantonese-speaking regions |
—
|
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: Cantonese-speaking regions | Statement: [Guan, hasNotableVariantUsageRegion, Cantonese-speaking regions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableVariantUsageRegion Context triple: [Guan, hasNotableVariantUsageRegion, Cantonese-speaking regions]
-
A.
hasNotableUsageRegion
chosen
Indicates that something is prominently or distinctively used within a particular geographic region.
-
B.
hasVariantUsage
Indicates that an entity is used in an alternative or non-standard way compared to its primary or canonical usage.
-
C.
hasNotabilityRegion
Indicates that an entity’s notability, prominence, or recognition is specifically associated with a particular geographic region.
-
D.
hasJurisdictionalVariant
Indicates that one entity is a version or form of another that applies specifically within a particular legal or administrative jurisdiction.
-
E.
usedInVariant
Indicates that something (such as a component, feature, or element) is utilized or included within a particular variant or version of a larger 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_69f043ed68a881909e858a06bab7a247 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69ff5285ed74819097e6e2a9084a079a |
completed | May 9, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69ff51fbe28881908ac8417dff9db81a |
completed | May 9, 2026, 3:25 p.m. |
Created at: April 28, 2026, 6:11 a.m.