Triple
T31995192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guilin chili sauce |
E816975
|
entity |
| Predicate | administrativeRegionOfOrigin |
P193134
|
FINISHED |
| Object | Guangxi |
—
|
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: Guangxi | Statement: [Guilin chili sauce, administrativeRegionOfOrigin, Guangxi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeRegionOfOrigin Context triple: [Guilin chili sauce, administrativeRegionOfOrigin, Guangxi]
-
A.
wasAdministrativeRegionFrom
Indicates that an entity served as an administrative region of another entity starting from a specified point in time.
-
B.
workOriginatesFrom
Indicates that the creation, development, or initiation of a work can be traced back to a particular source, agent, or origin.
-
C.
organizationCountryOfOrigin
Indicates the country where an organization was originally founded or established.
-
D.
countryOfOrigin
Indicates the country from which an entity originally comes or was first produced, created, or established.
-
E.
homelandRegion
Indicates that a region is recognized as the native or traditional homeland of a particular entity (such as a people, group, or organization).
- F. None of above. chosen
Provenance (4 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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
| PDg | Predicate description generation | batch_69fd389b653c81908a97ab2eff98c6ea |
completed | May 8, 2026, 1:12 a.m. |
Created at: May 1, 2026, 12:13 a.m.