Triple
T24192654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tòa án nhân dân tối cao |
E599741
|
entity |
| Predicate | chứcNăng |
P81043
|
FINISHED |
| Object | giám đốc việc xét xử của các tòa án khác |
—
|
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: giám đốc việc xét xử của các tòa án khác | Statement: [Tòa án nhân dân tối cao, chứcNăng, giám đốc việc xét xử của các tòa án khác]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chứcNăng Context triple: [Tòa án nhân dân tối cao, chứcNăng, giám đốc việc xét xử của các tòa án khác]
-
A.
기능
Indicates that an entity has a particular function, role, or operational capability.
-
B.
functie
chosen
Indicates that one entity serves as a function, role, or operational purpose in relation to another entity.
-
C.
providesFunctionalityOf
Indicates that one entity supplies, implements, or makes available the capabilities or functions that are normally associated with another entity.
-
D.
featuresAction
Indicates that one entity includes, presents, or showcases a particular action as a notable characteristic or component.
-
E.
featuresSuit
Indicates that one entity includes or presents a particular suit (e.g., clothing, armor, or outfit) as a notable component or attribute.
- 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_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:36 p.m.