Triple
T17809955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long Yun |
E444670
|
entity |
| Predicate | governmentFocus |
P1876
|
FINISHED |
| Object | regional stability and autonomy |
—
|
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: regional stability and autonomy | Statement: [Long Yun, governmentFocus, regional stability and autonomy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governmentFocus Context triple: [Long Yun, governmentFocus, regional stability and autonomy]
-
A.
policyFocus
chosen
Indicates that an entity (such as a person, organization, or document) is primarily concerned with, directed toward, or centered on a particular policy area or issue.
-
B.
governmentInvolvement
Indicates that a government participates in, influences, regulates, or otherwise plays a role in the specified activity, process, or entity.
-
C.
governmentalFunction
Indicates that an entity performs, embodies, or is responsible for an official role, duty, or activity of a government.
-
D.
governmentalCore
Indicates that something serves as a central, essential, or foundational part of a government or governmental system.
-
E.
governmentCategory
Indicates the type or classification of a government associated with an entity.
- 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_69d8b9f0de78819099395b14db75a8a6 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4887a50488190b9c148146ec607e6 |
completed | April 19, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:14 a.m.