Triple
T26478425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thanh Liem District |
E666103
|
entity |
| Predicate | belongsToISO3166-2ProvinceCode |
P164530
|
FINISHED |
| Object | VN-63 |
—
|
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: VN-63 | Statement: [Thanh Liem District, belongsToISO3166-2ProvinceCode, VN-63]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToISO3166-2ProvinceCode Context triple: [Thanh Liem District, belongsToISO3166-2ProvinceCode, VN-63]
-
A.
hasISO3166-2CodePrefix
Indicates that one entity’s ISO 3166-2 code begins with, or is prefixed by, the code of another entity.
-
B.
associatedProvinceOrState
Indicates that one entity is linked or related to a specific province or state as its relevant administrative region.
-
C.
hasProvinceEquivalent
Indicates that one administrative division is equivalent in status or function to a province within a given political or territorial system.
-
D.
hasProvinceName
Indicates that an entity (such as a province or region) bears or is associated with a specific province name.
-
E.
usesISO3166-2Code
chosen
Indicates that an entity employs or references a subdivision identifier defined by the ISO 3166-2 standard.
- 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_69ee883f80dc819090e311b022b78e02 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: April 27, 2026, 12:25 a.m.