Triple
T19212729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manas |
E480393
|
entity |
| Predicate | inTheosophyClassification |
P134999
|
FINISHED |
| Object | fifth principle |
—
|
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: fifth principle | Statement: [Manas, inTheosophyClassification, fifth principle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inTheosophyClassification Context triple: [Manas, inTheosophyClassification, fifth principle]
-
A.
spiritualityType
Indicates the specific kind or category of spirituality associated with an entity.
-
B.
typeOfDeity
Indicates that one entity is classified as a specific kind or category of deity in relation to another.
-
C.
spiritualityInfluencedBy
Indicates that one entity’s spirituality, spiritual beliefs, or practices are shaped, guided, or affected by another entity.
-
D.
typeOfTheology
Indicates the specific theological category, tradition, or system that characterizes a given religious belief, doctrine, or discourse.
-
E.
spiritualLineage
Indicates a relationship where one entity is connected to another through a chain of spiritual mentorship, transmission, or succession.
- F. None of above. chosen
Provenance (4 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_69d8e8cb8c348190b52075823911c869 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fa37fc7881908c53e332625dcdb4 |
completed | April 20, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69e4dcf22b3c8190bee02e3af946e114 |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4ddcf50108190a09d0f1291c17374 |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 1:21 p.m.