Triple
T30583604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anawrahta |
E778445
|
entity |
| Predicate | broughtFromThaton |
P33652
|
FINISHED |
| Object | Pali Buddhist scriptures |
—
|
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: Pali Buddhist scriptures | Statement: [Anawrahta, broughtFromThaton, Pali Buddhist scriptures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broughtFromThaton Context triple: [Anawrahta, broughtFromThaton, Pali Buddhist scriptures]
-
A.
broughtTo
Indicates that one entity caused another entity or object to be transported or accompanied to a particular destination or recipient.
-
B.
broughtOn
Indicates that one entity caused, initiated, or was responsible for the occurrence or introduction of another entity or event.
-
C.
broughtBack
Indicates that an entity caused another entity to return to a previous place, state, or condition.
-
D.
carriedFrom
chosen
Indicates that something was transported or moved away starting from a specified source location or origin.
-
E.
returnedFrom
Indicates that an entity has come back or been sent back from a specified source, location, or prior state.
- 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.