Triple
T24192722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TANDTC |
E599743
|
entity |
| Predicate | fullNameInVietnamese |
P32764
|
FINISHED |
| Object | Tòa án nhân dân tối cao |
—
|
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: Tòa án nhân dân tối cao | Statement: [TANDTC, fullNameInVietnamese, Tòa án nhân dân tối cao]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullNameInVietnamese Context triple: [TANDTC, fullNameInVietnamese, Tòa án nhân dân tối cao]
-
A.
nameInVietnamese
chosen
Indicates that one entity is the Vietnamese-language name or designation of another entity.
-
B.
nameOrderInVietnamese
Indicates the conventional ordering of a person's name components when written or spoken in Vietnamese.
-
C.
spouseNameInVietnamese
Indicates that the predicate specifies the name of a person's spouse as written or expressed in the Vietnamese language.
-
D.
fullNameInChineseGivenName
Indicates that the entity’s full name, when written in Chinese, is ordered with the given name first.
-
E.
fullName
Indicates that an entity has a complete personal name, typically combining given name(s) and family name into a single string.
- 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_69e288cdc8b88190bf2f835d3cb4ca28 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e2487db48190a17f77045d52334c |
completed | April 29, 2026, 10:49 a.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:36 p.m.