Triple
T16684324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thiệu Trị |
E405418
|
entity |
| Predicate | maintainedPolicyOf |
P31392
|
FINISHED |
| Object | isolation from Western powers |
—
|
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: isolation from Western powers | Statement: [Thiệu Trị, maintainedPolicyOf, isolation from Western powers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintainedPolicyOf Context triple: [Thiệu Trị, maintainedPolicyOf, isolation from Western powers]
-
A.
establishedPolicy
Indicates that a policy has been formally created, adopted, and put into effect as a guiding rule or standard.
-
B.
governingPolicy
Indicates that one entity serves as the authoritative policy or set of rules that directs, constrains, or regulates the behavior, operation, or decisions of another entity.
-
C.
endedPolicy
Indicates that a previously active policy has been brought to an end or terminated.
-
D.
soughtToMaintain
chosen
Indicates an entity’s deliberate effort or intention to keep another entity or condition in its existing state over time.
-
E.
usedPolicy
Indicates that an entity applied or followed a particular policy in carrying out an action or decision.
- 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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37d71a66881908c8d06cc074fdf29 |
completed | April 18, 2026, 12:47 p.m. |
| PD | Predicate disambiguation | batch_69e319bc73908190a0e38bc926b31f10 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:19 a.m.