Triple
T9944500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haizhu District |
E194167
|
entity |
| Predicate | isLocated |
P40
|
FINISHED |
| Object | south of central Guangzhou |
—
|
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: south of central Guangzhou | Statement: [Haizhu District, isLocated, south of central Guangzhou]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocated Context triple: [Haizhu District, isLocated, south of central Guangzhou]
-
A.
locatedIn
chosen
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
B.
hasLocationRole
Indicates that an entity holds or plays a specific role in relation to a particular location (e.g., origin, destination, storage site, or operational area).
-
C.
isAt
Indicates that one entity is located at or present in the place or position of another entity.
-
D.
timeLocatedIn
Indicates that an event, state, or entity occurs, exists, or is valid within a specified time or temporal interval.
-
E.
sometimesLocatedIn
Indicates that an entity is located in a given place only at certain times or under certain conditions, rather than permanently or always.
- 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_69ca82e409348190a393777356b80a2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb613fbb48190b82a06987310cc96 |
completed | April 2, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69cd1d97c44081908730071269f07712 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:45 p.m.