Triple
T32073949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aung Pyae Sone |
E819091
|
entity |
| Predicate | politicallyExposedPerson |
P195191
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Aung Pyae Sone, politicallyExposedPerson, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicallyExposedPerson Context triple: [Aung Pyae Sone, politicallyExposedPerson, true]
-
A.
occupationOfAssociatedPerson
Indicates the job or professional role held by a person who is associated with another referenced entity.
-
B.
previouslySanctionedBy
Indicates that an entity was subjected to formal sanctions or penalties by another entity at some earlier time.
-
C.
otherMajorSanctioningBodies
Indicates that there exist additional significant organizations or authorities, beyond a primary one, that impose or administer sanctions.
-
D.
countrySubjectToSanctions
Indicates that a country is currently facing formal sanctions or restrictive measures imposed by another state or international body.
-
E.
positionOnSanctions
Indicates a stance or viewpoint an entity holds regarding the use, implementation, or support of sanctions.
- 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69fdb04d37288190969a0f39d92efb49 |
completed | May 8, 2026, 9:43 a.m. |
Created at: May 1, 2026, 12:23 a.m.