Triple
T16869151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daw Thein Tin |
E410122
|
entity |
| Predicate | spouseDiplomaticRole |
P125296
|
FINISHED |
| Object | diplomat’s spouse |
—
|
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: diplomat’s spouse | Statement: [Daw Thein Tin, spouseDiplomaticRole, diplomat’s spouse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseDiplomaticRole Context triple: [Daw Thein Tin, spouseDiplomaticRole, diplomat’s spouse]
-
A.
spouseOffice
Indicates that one entity holds an office or position that is associated with, or held by, the spouse of another entity.
-
B.
spouseOfHeadOfState
Indicates that one person is the spouse (married partner) of a head of state.
-
C.
spouseOfCountry
Indicates that an entity is the spouse or marital partner of a person who is associated with, represents, or is from a specified country.
-
D.
spouseOfRole
Indicates that one role is the spouse (husband, wife, or equivalent marital partner) of another role.
-
E.
marriedToHeadOfGovernmentOf
Indicates that one entity is the spouse of the person who holds the position of head of government of the other 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b50a82348190b3e33fd558aa3c7f |
completed | April 18, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e355722040819098830dabf207ecd6 |
completed | April 18, 2026, 9:57 a.m. |
Created at: April 10, 2026, 5:24 a.m.