Triple
T24418750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VN |
E615665
|
entity |
| Predicate | associatedRegionCodeStandard |
P42695
|
FINISHED |
| Object | ISO 3166-2:VN |
—
|
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: ISO 3166-2:VN | Statement: [VN, associatedRegionCodeStandard, ISO 3166-2:VN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedRegionCodeStandard Context triple: [VN, associatedRegionCodeStandard, ISO 3166-2:VN]
-
A.
hasRegionCode
Indicates that an entity is associated with a specific regional identifier or code.
-
B.
regionCodeType
Indicates the classification or format type used for a given region code within a coding or identification system.
-
C.
registrationRegion
Indicates the geographic or administrative region in which an entity is officially registered.
-
D.
regionStandard
Indicates that something conforms to, is defined by, or is governed according to the official standards or norms of a particular region.
-
E.
ISO3166-2RegionCode
chosen
Indicates the standardized ISO 3166-2 code that specifies the particular primary administrative subdivision (such as a state, province, or region) to which an entity belongs.
- 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_69e2d7e9bfac8190a748952a90957106 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f296a12a50819099fcdbc7096b53dd |
completed | April 29, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:13 a.m.