Triple
T10576667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shramana |
E249626
|
entity |
| Predicate | textualAttestation |
P60064
|
FINISHED |
| Object | early Buddhist texts |
—
|
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: early Buddhist texts | Statement: [Shramana, textualAttestation, early Buddhist texts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textualAttestation Context triple: [Shramana, textualAttestation, early Buddhist texts]
-
A.
attestation
Indicates a formal declaration or confirmation that something is true, accurate, or has been verified.
-
B.
languageOfAttestation
Indicates the language in which a statement, document, or evidence is originally recorded or attested.
-
C.
attestedBy
Indicates that the existence, occurrence, or validity of something is supported, confirmed, or documented by a specified source or authority.
-
D.
scriptOfAttestation
Indicates the writing system or script in which an attestation (recorded instance) of something is written.
-
E.
alsoAttestedIn
chosen
Indicates that the same item, fact, or phenomenon is recorded or evidenced in another source, context, or location as well.
- 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5275628988190bd00dd3f8d7c3937 |
completed | April 7, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69d51901ff6c819095e7b528170a69dc |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:38 p.m.