Triple
T32306205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mingun Pahtodawgyi |
E825376
|
entity |
| Predicate | builderIntention |
P88492
|
FINISHED |
| Object | to demonstrate royal merit and power |
—
|
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: to demonstrate royal merit and power | Statement: [Mingun Pahtodawgyi, builderIntention, to demonstrate royal merit and power]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builderIntention Context triple: [Mingun Pahtodawgyi, builderIntention, to demonstrate royal merit and power]
-
A.
builder
Indicates that an entity is responsible for constructing, creating, or assembling another entity.
-
B.
intendedWith
Indicates that one entity is the planned or desired target, recipient, or context for the use or application of another entity.
-
C.
intendedProject
Indicates that an entity is the planned or targeted project associated with another entity (such as a person, organization, or activity).
-
D.
intendsTo
chosen
Indicates that one entity has the purpose, plan, or desire to perform an action involving another entity or outcome.
-
E.
builderModel
Indicates a relationship where one entity serves as the design or construction template (the "builder model") used to create, configure, or generate 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_69f349115304819084ee91d345b6c8aa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bd81235081908c0748dfd5db5039 |
completed | May 3, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:45 a.m.