Triple
T24315329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hai Phong municipal authorities |
E612791
|
entity |
| Predicate | governsTypeOfCity |
P57766
|
FINISHED |
| Object | port city |
—
|
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: port city | Statement: [Hai Phong municipal authorities, governsTypeOfCity, port city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsTypeOfCity Context triple: [Hai Phong municipal authorities, governsTypeOfCity, port city]
-
A.
governedCityStateType
Indicates that a city is governed under a particular type or form of state-level governance.
-
B.
hasCityGovernmentType
Indicates the specific form or structure of municipal governance that administers a city.
-
C.
capitalCityGoverningFrom
Indicates that a specified capital city serves as the administrative center from which a given political entity is governed.
-
D.
governsRegionWithLargestCity
Indicates that a governing entity has authority over the region that contains the largest city in a specified area or jurisdiction.
-
E.
cityServedType
chosen
Indicates the type or category of city that is served by a given entity (such as a facility, service, or infrastructure).
- 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_69e2d7da491c8190b6e6218af50923db |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292a6f2c48190b6266fd6c3d6391a |
completed | April 29, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f1c45f45888190a9ccc225906c34bd |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 1:46 a.m.