Triple
T16169464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kedukan Bukit |
E392395
|
entity |
| Predicate | inscriptionEra |
P33352
|
FINISHED |
| Object | 7th century |
—
|
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: 7th century | Statement: [Kedukan Bukit, inscriptionEra, 7th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inscriptionEra Context triple: [Kedukan Bukit, inscriptionEra, 7th century]
-
A.
inscriptionDating
chosen
Indicates the temporal period or specific date to which an inscription is assigned or attributed.
-
B.
inscriptionType
Indicates the specific kind or category of inscription associated with an entity (e.g., dedicatory, funerary, commemorative).
-
C.
inscription
Indicates that text has been written, carved, or engraved onto a surface or object.
-
D.
marksNewEraFor
Indicates that one event, development, or change signifies the beginning of a distinct new period or phase for another.
-
E.
inscriptionDate
Indicates the date on which an inscription was created, carved, or formally recorded.
- 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.