Triple
T11361329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinese Thais |
E269092
|
entity |
| Predicate | primaryAncestralRegions |
P19688
|
FINISHED |
| Object | southern China |
—
|
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: southern China | Statement: [Chinese Thais, primaryAncestralRegions, southern China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAncestralRegions Context triple: [Chinese Thais, primaryAncestralRegions, southern China]
-
A.
secondaryAncestralHomeland
Indicates a place that serves as an additional or subsequent ancestral homeland for a group or lineage, distinct from their primary place of origin.
-
B.
primaryAncestralCountry
Indicates the country that is considered the main place of origin for an individual’s or group’s ancestors.
-
C.
foundingRegion
Indicates the geographic region where an entity (such as an organization, movement, or institution) was originally founded.
-
D.
originSubregion
Indicates the specific subregional area from which an entity originates or is derived.
-
E.
ethnogenesisRegion
chosen
Indicates the geographic region where the formation or emergence of an ethnic group took place.
- 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_69d6aacbe18081909e5fadb50082dd96 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d800160a1c81909d115bf89fe54a49 |
completed | April 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69d7e7022d508190996f9be0847c2b41 |
completed | April 9, 2026, 5:50 p.m. |
Created at: April 8, 2026, 9:33 p.m.