Triple
T8707465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | To Mock a Mockingbird |
E206683
|
entity |
| Predicate | didacticApproach |
P779
|
FINISHED |
| Object | puzzle-based exposition |
—
|
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: puzzle-based exposition | Statement: [To Mock a Mockingbird, didacticApproach, puzzle-based exposition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: didacticApproach Context triple: [To Mock a Mockingbird, didacticApproach, puzzle-based exposition]
-
A.
didacticPurpose
Indicates that something is intended to teach, instruct, or convey educational content or guidance.
-
B.
educationalApproach
chosen
Indicates the method, strategy, or philosophy used to guide teaching and learning within an educational context.
-
C.
didacticCharacter
Indicates that one entity serves a teaching or instructional role toward another, conveying guidance, lessons, or moral instruction.
-
D.
academicApproach
Indicates an entity’s characteristic method, strategy, or style used in academic work, study, or instruction.
-
E.
typeOfTeaching
Indicates the specific method or style of teaching used in an instructional 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_69ca835645e881908f00e3c8b51da81d |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc58fe19ac8190936ba0faf513ed2b |
completed | March 31, 2026, 11:30 p.m. |
| PD | Predicate disambiguation | batch_69cc456bda508190a9aa0fb92760739e |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:35 p.m.