Triple
T34733308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Min Saw Mon |
E1001271
|
entity |
| Predicate | eraUsheredIn |
P6373
|
FINISHED |
| Object | Mrauk U period |
E304684
|
NE 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: Mrauk U period | Statement: [Min Saw Mon, eraUsheredIn, Mrauk U period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraUsheredIn Context triple: [Min Saw Mon, eraUsheredIn, Mrauk U period]
-
A.
historicalEraUsheredIn
chosen
Indicates the historical era or period that was initiated or brought about as a result of a particular event, action, or entity.
-
B.
inauguratedWith
Indicates that an event, position, or institution was formally initiated or opened through a specific ceremony, action, or accompanying element.
-
C.
inauguratedReignOf
Indicates that one entity formally began or initiated the period of rule or reign of another entity.
-
D.
eraOfBreakthrough
Indicates the time period during which a significant breakthrough or major advancement occurred.
-
E.
inauguratedAsPartOf
Indicates that an inauguration event occurred as a component or phase of a larger event, process, or initiative.
- F. None of above.
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_69f76daf739881909ed3554f98a2b433 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a375befa54c81909a986c2081739681 |
completed | June 21, 2026, 3:35 a.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.