Triple
T17939712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sutta Pitaka |
E448553
|
entity |
| Predicate | writtenDownInScript |
P12727
|
FINISHED |
| Object | Sinhala script (historically) |
—
|
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: Sinhala script (historically) | Statement: [Sutta Pitaka, writtenDownInScript, Sinhala script (historically)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writtenDownInScript Context triple: [Sutta Pitaka, writtenDownInScript, Sinhala script (historically)]
-
A.
writtenIn
chosen
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
-
B.
willWrittenIn
Indicates that a legal will was authored, drafted, or formally written in a specified location or jurisdiction.
-
C.
wroteIn
Indicates that an entity authored or composed something using a particular language, medium, or writing system.
-
D.
written
Indicates that one entity has created or authored a text, document, or written work involving or about another entity.
-
E.
writtenInKey
Indicates that a musical work, passage, or section is composed using a particular key as its tonal center.
- 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4ad9533688190bff773c183ed8505 |
completed | April 19, 2026, 10:25 a.m. |
| PD | Predicate disambiguation | batch_69e3f8e713d481908b4a126258c18b63 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:21 a.m.