Triple
T24400701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Da Nang Port Joint Stock Company |
E615156
|
entity |
| Predicate | hasOfficialNameInVietnamese |
P32764
|
FINISHED |
| Object | Công ty Cổ phần Cảng Đà Nẵng |
—
|
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: Công ty Cổ phần Cảng Đà Nẵng | Statement: [Da Nang Port Joint Stock Company, hasOfficialNameInVietnamese, Công ty Cổ phần Cảng Đà Nẵng]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialNameInVietnamese Context triple: [Da Nang Port Joint Stock Company, hasOfficialNameInVietnamese, Công ty Cổ phần Cảng Đà Nẵng]
-
A.
hasOfficialNameInJapanese
Indicates that an entity has an official, formally recognized name expressed in the Japanese language.
-
B.
hasOfficialNameInFilipino
Indicates that an entity has an official or formally recognized name expressed in the Filipino language.
-
C.
nameInVietnamese
chosen
Indicates that one entity is the Vietnamese-language name or designation of another entity.
-
D.
hasOfficialNameInEnglish
Indicates that an entity has an officially recognized name expressed in the English language.
-
E.
hasOfficialNameInNepali
Indicates that an entity has an official name expressed in the Nepali language.
- 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_69e2d7e780bc81908049c779e697a7f6 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f294da48348190bcdcab21209deaac |
completed | April 29, 2026, 11:31 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:05 a.m.