Triple
T17980918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kundalini |
E449597
|
entity |
| Predicate | guidanceRecommended |
P129993
|
FINISHED |
| Object | qualified teacher |
—
|
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: qualified teacher | Statement: [Kundalini, guidanceRecommended, qualified teacher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guidanceRecommended Context triple: [Kundalini, guidanceRecommended, qualified teacher]
-
A.
recommendedIn
Indicates that one entity is suggested or endorsed within the context, content, or scope of another entity (such as a document, list, or recommendation source).
-
B.
commendedFor
Indicates that one entity has expressed praise or approval toward another entity specifically because of a particular action, quality, or achievement.
-
C.
guidanceType
Indicates the specific kind or category of guidance being provided or referenced in the relationship between entities.
-
D.
providesGuidanceTo
Indicates that one entity offers direction, advice, or instruction to another entity.
-
E.
recitationRecommended
Indicates that a particular recitation session or section is recommended for an entity, such as a student or course.
- 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b20431588190a5fe2148a61de403 |
completed | April 19, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:22 a.m.