Triple
T24192691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tòa án nhân dân tối cao |
E599741
|
entity |
| Predicate | chịuSựĐiềuChỉnhCủa |
P155123
|
FINISHED |
| Object | Luật Tổ chức Tòa án nhân dân |
—
|
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: Luật Tổ chức Tòa án nhân dân | Statement: [Tòa án nhân dân tối cao, chịuSựĐiềuChỉnhCủa, Luật Tổ chức Tòa án nhân dân]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chịuSựĐiềuChỉnhCủa Context triple: [Tòa án nhân dân tối cao, chịuSựĐiềuChỉnhCủa, Luật Tổ chức Tòa án nhân dân]
-
A.
adjustsFor
Indicates that one entity modifies, compensates, or accounts for the effects of another entity to achieve a corrected or normalized result.
-
B.
adjustmentType
Indicates the specific kind or category of modification applied to an existing value, state, or configuration within the relationship.
-
C.
modification
Indicates a change made to an existing entity, altering its properties, structure, or state from a prior version.
-
D.
modulates
Indicates that one entity adjusts, regulates, or alters the intensity, frequency, or effect of another entity or process.
-
E.
changesWith
Indicates that one entity varies or is modified in response to changes in another entity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f1c9834064819082024233d9c6f98f |
completed | April 29, 2026, 9:04 a.m. |
Created at: April 17, 2026, 11:36 p.m.