Triple
T9188794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hạ Đình Ward |
E220525
|
entity |
| Predicate | appliesMunicipalRegulation |
P16838
|
FINISHED |
| Object | regulations 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: regulations of Hanoi | Statement: [Hạ Đình Ward, appliesMunicipalRegulation, regulations of Hanoi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesMunicipalRegulation Context triple: [Hạ Đình Ward, appliesMunicipalRegulation, regulations of Hanoi]
-
A.
hasLocalOrdinances
chosen
Indicates that a governing body or jurisdiction has established and enacted specific local ordinances or regulations.
-
B.
usesMunicipalGovernmentAct
Indicates that an entity operates under, applies, or is governed by the provisions of a Municipal Government Act.
-
C.
isInMunicipality
Indicates that one entity (typically a place or address) is located within the administrative boundaries of a specific municipality.
-
D.
isMunicipal
Indicates that something belongs to, is administered by, or is characteristic of a municipality or local city government.
-
E.
affectsMunicipality
Indicates that one entity has an impact on, influences, or brings about changes in a specific municipality.
- 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_69ca83e6d77c81909862b7afef56b1bf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccc31d91d48190b8b8874e09c84404 |
completed | April 1, 2026, 7:02 a.m. |
| PD | Predicate disambiguation | batch_69cc66090e5881908889dc1213815626 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:24 p.m.