Triple
T8833970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liễu Giai Ward |
E210216
|
entity |
| Predicate | isPartOfUrbanDistrictType |
P84910
|
FINISHED |
| Object | inner-city district of Hanoi |
—
|
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: inner-city district of Hanoi | Statement: [Liễu Giai Ward, isPartOfUrbanDistrictType, inner-city district of Hanoi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfUrbanDistrictType Context triple: [Liễu Giai Ward, isPartOfUrbanDistrictType, inner-city district of Hanoi]
-
A.
isUrbanConstituency
Indicates that a given constituency is classified as urban rather than rural or semi-urban.
-
B.
isUrbanDistrict
Indicates that a given district is classified as an urban administrative or residential area rather than a rural one.
-
C.
hasUrbanDistrictFunction
Indicates that an entity serves the administrative or functional role of an urban district within a larger territorial or governance structure.
-
D.
containsUrbanArea
Indicates that a geographic region fully or partially encompasses an urbanized area within its boundaries.
-
E.
hasUrbanDistrictCount
Indicates the number of urban districts associated with a given entity.
- 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_69ca8388549c819095fd94eadefbb007 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60670fa48190b2a873f6498de7f6 |
completed | April 1, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69cc5c23d08481908d8c9b0ad3d1dc00 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cff3608819081d2d7e5c16d44b7 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:47 p.m.