Triple
T16169489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kedukan Bukit |
E392395
|
entity |
| Predicate | currentLocationOfInscription |
P109545
|
FINISHED |
| Object | Indonesia (museum collection) |
—
|
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: Indonesia (museum collection) | Statement: [Kedukan Bukit, currentLocationOfInscription, Indonesia (museum collection)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentLocationOfInscription Context triple: [Kedukan Bukit, currentLocationOfInscription, Indonesia (museum collection)]
-
A.
inscriptionsFoundAt
Indicates that inscriptions are discovered or located at a particular place or site.
-
B.
cultLocation
Indicates that a cult or religious group is based in, practices in, or is primarily associated with a particular location.
-
C.
isLocatedOn
Indicates that one entity exists at or is situated upon the surface or area of another entity.
-
D.
inscribedAt
chosen
Indicates that an entity is formally recorded, registered, or written onto a specific object, surface, or official list at a particular place or institution.
-
E.
monumentsLocation
Indicates the geographical place where a monument is situated or located.
- 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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21eb5e6d881908749683091afa90c |
completed | April 17, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_69e219d642708190ba31a90dce76a210 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.