Triple
T1083518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indology |
E23999
|
entity |
| Predicate | studiesAspect |
P16979
|
FINISHED |
| Object | ancient Indian religions |
—
|
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 Indian religions | Statement: [Indology, studiesAspect, ancient Indian religions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studiesAspect Context triple: [Indology, studiesAspect, ancient Indian religions]
-
A.
partOfStudy
Indicates that something is a component, segment, or subset within a larger study or research project.
-
B.
studiedBy
Indicates that a subject (such as a field, topic, or object) is examined, researched, or learned by an agent (such as a person or group).
-
C.
academicFocus
Indicates the primary field of study, discipline, or subject area that an entity concentrates on academically.
-
D.
notableObjectOfStudy
chosen
Indicates that a subject is a significant or prominent focus of research, analysis, or scholarly attention for another entity.
-
E.
researchStrength
Indicates the degree to which an entity possesses strong capabilities, performance, or impact in conducting research.
- 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_69a49404428c819092dcc9632f5f7b8b |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b95e56948190a1e92367ad7240b7 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b73f4310819086281f8ec67d1a32 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.