Triple
T30583726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shwebo |
E778448
|
entity |
| Predicate | wasRoyalSeatOf |
P38122
|
FINISHED |
| Object | Alaungpaya |
—
|
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: Alaungpaya | Statement: [Shwebo, wasRoyalSeatOf, Alaungpaya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasRoyalSeatOf Context triple: [Shwebo, wasRoyalSeatOf, Alaungpaya]
-
A.
ancestralSeatOf
Indicates that one entity is the traditional or original home, origin place, or foundational location associated with the lineage, heritage, or authority of another entity.
-
B.
wasRoyalCityOf
Indicates that a city formerly served as the royal or principal city (such as a capital or main seat of power) of a specified kingdom, dynasty, or ruling authority.
-
C.
capitalOfRealmDuringReign
Indicates that a particular city or place served as the capital of a realm specifically during the time span of a given ruler’s reign.
-
D.
usedAsSeatOfPowerBy
chosen
Indicates that something serves as the primary location or base from which an individual or group exercises authority, control, or governance.
-
E.
capitalOfHisKingdom
Indicates that one entity serves as the capital city of the kingdom ruled or possessed by another 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_69f224a04b248190b0ca443ec86207b8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68945093481909c6eba86bc50870e |
completed | May 2, 2026, 11:31 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:23 p.m.