Triple
T29916407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teochew embroidery |
E759805
|
entity |
| Predicate | majorCityAssociation |
P111468
|
FINISHED |
| Object | Chaozhou |
—
|
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: Chaozhou | Statement: [Teochew embroidery, majorCityAssociation, Chaozhou]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorCityAssociation Context triple: [Teochew embroidery, majorCityAssociation, Chaozhou]
-
A.
cityAssociatedWith
Indicates that there is a notable connection or relationship between a city and another entity, such as relevance, involvement, or contextual association.
-
B.
capitalCityAssociation
Indicates a relationship where one entity serves as the capital city of another entity, such as a country, state, or region.
-
C.
majorCityInCountry
Indicates that a city is a primary or significant urban center within a specified country.
-
D.
majorAffiliateCity
chosen
Indicates that a city serves as a primary or significant affiliate location associated with another entity.
-
E.
majorCityAlong
Indicates that a major city is located along the course or path of a specified geographic feature, such as a river, road, or route.
- 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_69f2246189fc8190996b63ee1f9a2374 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: April 29, 2026, 6:12 p.m.