Triple
T29688950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 胡 |
E751161
|
entity |
| Predicate | surnameUsageRegion |
P99565
|
FINISHED |
| Object | Mainland China |
—
|
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: Mainland China | Statement: [胡, surnameUsageRegion, Mainland China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surnameUsageRegion Context triple: [胡, surnameUsageRegion, Mainland China]
-
A.
usedAsSurnameInCountry
Indicates that a particular name functions as a family surname within the specified country.
-
B.
namePopularityRegion
chosen
Indicates the geographic region or area in which a particular name has a certain level of popularity or usage.
-
C.
givenNameUsageCountry
Indicates the country in which a particular given name is used or commonly found.
-
D.
hasNameGenderUsage
Indicates that a particular name is used with a specific gender or set of genders in a given context.
-
E.
surnameUsedIn
Indicates that a particular surname is used or borne within a specified context, such as by a person, family, or 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f67292c75c8190a09ab2fb88fc1a33 |
completed | May 2, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:15 p.m.