Triple
T10669405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hưng Yên Province |
E251444
|
entity |
| Predicate | countryCode |
P208
|
FINISHED |
| Object | VN |
E615665
|
NE 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 | Statement: [Hưng Yên Province, countryCode, VN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VN Context triple: [Hưng Yên Province, countryCode, VN]
-
A.
VN
VN is the IATA airline designator assigned to Vietnam Airlines, the national flag carrier of Vietnam.
-
B.
VN
chosen
VN is the ISO 3166-1 alpha-2 country code for Vietnam, a Southeast Asian nation known for its history, diverse landscapes, and rapidly growing economy.
-
C.
Vietnamese
Vietnamese refers to the people, language, and culture associated with Vietnam, a Southeast Asian country with a rich history and distinct cultural traditions.
-
D.
Viet
Viet refers to the ethnic Vietnamese people, the majority ethnic group of Vietnam with a distinct language and culture.
-
E.
VNKT
VNKT is the ICAO airport code for Tribhuvan International Airport, the main international gateway serving Kathmandu, Nepal.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aa5b0d2881909584b20efc5877f0 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6f861513881909b44c711371086b7 |
completed | April 9, 2026, 12:52 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d98865f700819093c8cadc6fcef75f |
completed | April 10, 2026, 11:31 p.m. |
Created at: April 8, 2026, 9:09 p.m.