Triple
T34110439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supayalay |
E874823
|
entity |
| Predicate | wasQueenConsortOf |
P59097
|
FINISHED |
| Object | Thibaw Min |
—
|
NE NERFINISHED |
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: Thibaw Min | Statement: [Supayalay, wasQueenConsortOf, Thibaw Min]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasQueenConsortOf Context triple: [Supayalay, wasQueenConsortOf, Thibaw Min]
-
A.
reignAsQueenConsortFrom
Indicates the time period during which a person held the role of queen consort, starting from a specified date or event.
-
B.
producedQueenConsort
Indicates that one entity gave rise to or is the origin of another entity who became a queen consort.
-
C.
reignAsQueenConsort
chosen
Indicates that a person holds the position and performs the role of queen consort during the reign of a monarch.
-
D.
marriedToWidowedQueenOf
Indicates that one entity is married to a person who is the widowed queen of another specified entity (typically a realm or ruler).
-
E.
typeOfMonarchConsort
Indicates the specific kind or category of monarch’s spouse (consort) that an entity is, such as queen consort, prince consort, or empress consort.
- 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_69f349a80d4481908527317d43f5c579 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70cb47b9c8190a479877960b256a6 |
completed | May 3, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:53 a.m.