Triple
T28651784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fóshān |
E725219
|
entity |
| Predicate | representsToponym |
P160456
|
FINISHED |
| Object | Foshan |
—
|
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: Foshan | Statement: [Fóshān, representsToponym, Foshan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsToponym Context triple: [Fóshān, representsToponym, Foshan]
-
A.
isToponymic
Indicates that something is related to or derived from a place name (a toponym).
-
B.
includesToponym
Indicates that one entity contains or references a place name (toponym) associated with another entity.
-
C.
isToponymOf
chosen
Indicates that one entity is a place name (toponym) that refers to the location represented by the other entity.
-
D.
hasToponymy
Indicates a relationship where one entity possesses or is associated with the system, study, or set of place names (toponyms) of another entity.
-
E.
isToponymIn
Indicates that a place name (toponym) is located within or refers to a specific geographic area or region.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: April 28, 2026, 4:52 a.m.