Triple
T34616976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moodabidri |
E888888
|
entity |
| Predicate | containsManuscripts |
P202398
|
FINISHED |
| Object | ancient Jain palm-leaf manuscripts |
—
|
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: ancient Jain palm-leaf manuscripts | Statement: [Moodabidri, containsManuscripts, ancient Jain palm-leaf manuscripts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsManuscripts Context triple: [Moodabidri, containsManuscripts, ancient Jain palm-leaf manuscripts]
-
A.
areManuscriptsOf
Indicates that the subject entities are manuscripts that are versions, copies, or instances of the work represented by the object entity.
-
B.
manuscriptsContainingWorks
Indicates that certain manuscripts include or contain specific works within them.
-
C.
hasManuscriptsIn
Indicates that an entity possesses or is associated with manuscripts that are located in a specified place or collection.
-
D.
copiedManuscriptsOf
Indicates that one entity has produced or created handwritten reproductions of the manuscripts belonging to another entity.
-
E.
manuscriptFoundIn
Indicates that a manuscript is discovered or located within a particular place, collection, or context.
- F. None of above. chosen
Provenance (4 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_69f349d584e08190b40b9f6281ad50c4 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a0079e152648190a9da2add94fc1831 |
completed | May 10, 2026, 12:28 p.m. |
| PD | Predicate disambiguation | batch_6a0078f77f9c8190af357a6016a2bd53 |
completed | May 10, 2026, 12:24 p.m. |
| PDg | Predicate description generation | batch_6a0079e0a9688190a420759fafd47807 |
completed | May 10, 2026, 12:28 p.m. |
Created at: May 1, 2026, 2:03 a.m.