Triple
T29128909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Thai Binh |
E738310
|
entity |
| Predicate | provinceCenter |
P110991
|
FINISHED |
| Object | Hanoi |
—
|
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: Hanoi | Statement: [Diocese of Thai Binh, provinceCenter, Hanoi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: provinceCenter Context triple: [Diocese of Thai Binh, provinceCenter, Hanoi]
-
A.
provinceHeadquarters
chosen
Indicates that one entity serves as the main administrative or organizational headquarters for a province associated with the other entity.
-
B.
provinceSeatLocatedIn
Indicates that the administrative seat or capital of a province is located within a specified geographic or political area.
-
C.
populationCenterRegion
Indicates the broader geographic region within which a given population center is located.
-
D.
coCapitalOf
Indicates that two or more cities share the status of being capital cities of the same political or administrative entity.
-
E.
provinceCapitalLocatedOn
Indicates that the capital of a province is geographically situated on or alongside a specified physical feature or location (such as a river, coast, or lake).
- 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_69f07cb29cdc8190afa55444553de60c |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: April 28, 2026, 11:30 a.m.