Triple
T28740966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Hung Hoa |
E731238
|
entity |
| Predicate | provinceCivil |
P188424
|
FINISHED |
| Object | Hà Nội municipality |
—
|
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: Hà Nội municipality | Statement: [Diocese of Hung Hoa, provinceCivil, Hà Nội municipality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: provinceCivil Context triple: [Diocese of Hung Hoa, provinceCivil, Hà Nội municipality]
-
A.
province
Indicates that one entity is an administrative subdivision or region (a province) governed by or belonging to another, typically larger, political or territorial entity.
-
B.
provinceOfficial
Indicates that an individual holds an official governmental position within a specific province.
-
C.
isProvincial
Indicates that something belongs to, is characteristic of, or is administered at the level of a province rather than a national or local level.
-
D.
municipalProvince
Indicates that a municipality is administratively located within or governed as part of a specific province.
-
E.
provincialLevelAuthority
Indicates that an entity holds official governing or administrative authority at the provincial (sub-national) level.
- 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_69f043ecb5c081909ec9da1172d68ece |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba789c1188190973a919bfe2871f3 |
completed | May 6, 2026, 8:41 p.m. |
Created at: April 28, 2026, 6:02 a.m.