Triple
T9192912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Mon |
E220631
|
entity |
| Predicate | notableCorpusType |
P32641
|
FINISHED |
| Object | royal foundation inscriptions |
—
|
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: royal foundation inscriptions | Statement: [Old Mon, notableCorpusType, royal foundation inscriptions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCorpusType Context triple: [Old Mon, notableCorpusType, royal foundation inscriptions]
-
A.
hasNotableCorpus
Indicates that an entity possesses a significant, well-recognized body of work, texts, or collected materials associated with it.
-
B.
primaryCorpusType
chosen
Indicates the main or dominant type or category of corpus associated with an entity.
-
C.
corpus
Indicates that an entity is a collection or body of texts, documents, or linguistic data used as a unified set for analysis or reference.
-
D.
notableCategoryType
Indicates that an entity is notably associated with or classified under a particular category type.
-
E.
notableContentType
Indicates the type or category of content for which an entity is notable or best known.
- 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_69ca83e7ba70819088b74866d9da2c30 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd5c1fa9c8190bc5cc6dce8778694 |
completed | April 1, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69cc66090e5881908889dc1213815626 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:24 p.m.