Triple
T17936897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ajivika tradition |
E448490
|
entity |
| Predicate | scripturesStatus |
P16327
|
FINISHED |
| Object | original texts lost |
—
|
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: original texts lost | Statement: [Ajivika tradition, scripturesStatus, original texts lost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scripturesStatus Context triple: [Ajivika tradition, scripturesStatus, original texts lost]
-
A.
scripturalStatus
chosen
Indicates the relationship between a text and its recognition or classification as scriptural, canonical, or authoritative within a religious or doctrinal tradition.
-
B.
scripturalCanonStatus
Indicates whether and how a text is recognized as part of an authoritative scriptural canon within a given religious or doctrinal tradition.
-
C.
biblicalStatus
Indicates that one entity has a particular standing, role, or classification within a biblical or scriptural context in relation to another entity.
-
D.
hasScripture
Indicates that one entity possesses, is associated with, or is defined by a particular scripture or set of scriptural texts.
-
E.
recognizesScripturesFrom
Indicates that one entity acknowledges or accepts certain scriptures as authoritative or valid based on another entity as their source or origin.
- 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_69e4ad924f6c8190a0d676dfa20c9918 |
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.