Triple
T6872925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samkhyakarika |
E158595
|
entity |
| Predicate | isCoreTextOf |
P11293
|
FINISHED |
| Object | classical Samkhya curriculum |
—
|
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: classical Samkhya curriculum | Statement: [Samkhyakarika, isCoreTextOf, classical Samkhya curriculum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCoreTextOf Context triple: [Samkhyakarika, isCoreTextOf, classical Samkhya curriculum]
-
A.
coreText
chosen
Indicates that something serves as the main or primary textual content within a larger work or context.
-
B.
isCoreComponentOf
Indicates that something is an essential, foundational part required for the structure, function, or identity of another entity.
-
C.
hasCore
Indicates that one entity possesses, contains, or is built around a central or most essential component represented by another entity.
-
D.
textContent
Indicates that one entity is the textual content or written material contained within another entity.
-
E.
isNucleusOf
Indicates that one entity functions as the central or most important core component of another entity.
- 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_69c68832af1481908ce356e133ebaebe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d8c73ea08190b6bb1463e7ead47b |
completed | March 27, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b363dc8190a7225b540ab2bc40 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:22 p.m.