Triple
T14297828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palapa Oath |
E354486
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Majapahit-era text |
C14719
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Majapahit-era text Context triple: [Palapa Oath, instanceOf, Majapahit-era text]
-
A.
Old Javanese inscription
chosen
An Old Javanese inscription is a historical text carved or written in the Old Javanese language, typically on stone, metal, or other durable materials, documenting political, religious, legal, or social matters in ancient Java.
-
B.
ancient Javanese inscription
An ancient Javanese inscription is a historical text carved or written in Old Javanese script on durable materials such as stone, metal, or clay, documenting religious, political, legal, or cultural aspects of early Javanese civilization.
-
C.
Srivijaya inscription
A Srivijaya inscription is an ancient written record, typically in Old Malay or Sanskrit, produced by the Srivijaya maritime empire to document royal decrees, religious dedications, political events, or administrative matters.
-
D.
Javanese historical event
A Javanese historical event is a significant occurrence in the past that took place in Java or involved Javanese people, shaping the island’s political, social, cultural, or religious development.
-
E.
Srivijayan inscription
A Srivijayan inscription is an ancient written record, typically carved in stone or metal, produced under the Srivijaya maritime empire to document royal decrees, religious dedications, political events, or administrative matters.
- F. None of above.
Provenance (1 batch)
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_69d8278e17088190b328c5a9d4be74ff |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:11 a.m.