Triple
T19595977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seri Rama |
E470348
|
entity |
| Predicate | adaptationContext |
P2375
|
FINISHED |
| Object | Islamicate Malay court literature |
—
|
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: Islamicate Malay court literature | Statement: [Seri Rama, adaptationContext, Islamicate Malay court literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adaptationContext Context triple: [Seri Rama, adaptationContext, Islamicate Malay court literature]
-
A.
adaptationIn
Indicates that something appears, is represented, or takes place within a particular adaptation of an original work.
-
B.
adaptationType
chosen
Indicates the specific kind or category of adaptation that relates one entity to another or to a particular context.
-
C.
adaptation
Indicates a relationship where one entity changes or is modified to better suit, function within, or correspond to another entity or context.
-
D.
isAdaptation
Indicates that one work is derived from, based on, or reinterprets the content of another work.
-
E.
acquisitionContext
Indicates the circumstances, conditions, or setting under which an acquisition or purchase takes place.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e6407a09608190aa1df92f8c21f9e7 |
completed | April 20, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69e514e166dc8190a0f147e0b4c8bbe7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.