Triple
T13886076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charitropakhyan |
E333845
|
entity |
| Predicate | didacticMethod |
P24055
|
FINISHED |
| Object | use of exempla (illustrative stories) |
—
|
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: use of exempla (illustrative stories) | Statement: [Charitropakhyan, didacticMethod, use of exempla (illustrative stories)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: didacticMethod Context triple: [Charitropakhyan, didacticMethod, use of exempla (illustrative stories)]
-
A.
didacticPurpose
Indicates that something is intended to teach, instruct, or convey educational content or guidance.
-
B.
typeOfTeaching
chosen
Indicates the specific method or style of teaching used in an instructional context.
-
C.
coreTeaching
Indicates that an entity serves as a primary or foundational teaching or instructional activity for another entity.
-
D.
definedTeaching
Indicates that one entity has formally specified or established the teaching content, method, or curriculum for another entity.
-
E.
educationalApproach
Indicates the method, strategy, or philosophy used to guide teaching and learning within an educational context.
- 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_69d81c5dd2d48190b7a5fc1e009de936 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de23a101488190bd790b28033d38b9 |
completed | April 14, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69de05972f3881909977b4c843984f88 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:15 p.m.