Triple
T25161422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Order |
E626449
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indonesian historical era |
C49813
|
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: Indonesian historical era Context triple: [Old Order, instanceOf, Indonesian historical era]
-
A.
Javanese historical era
A Javanese historical era is a distinct period in the history of the Javanese people, defined by characteristic political structures, cultural developments, and social transformations on the island of Java.
-
B.
regency of Indonesia
A regency of Indonesia is a second-level administrative division, below a province, governed by a regent and responsible for managing local governance, public services, and regional development within its territory.
-
C.
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.
-
D.
Majapahit-era monument
A Majapahit-era monument is a historical structure or site originating from the Majapahit Kingdom (circa 13th–16th centuries) that reflects its distinctive architectural style, religious syncretism, and political or cultural significance in maritime Southeast Asia.
-
E.
Javanese dynasty
A Javanese dynasty is a ruling lineage or royal house originating from the island of Java, Indonesia, that holds political, cultural, and spiritual authority over a Javanese kingdom or realm across generations.
- F. None of above. chosen
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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 6:31 a.m.