Triple
T5094385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ælfric’s Grammar |
E114830
|
entity |
| Predicate | educationalAudience |
P12602
|
FINISHED |
| Object | Anglo-Saxon students |
—
|
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: Anglo-Saxon students | Statement: [Ælfric’s Grammar, educationalAudience, Anglo-Saxon students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: educationalAudience Context triple: [Ælfric’s Grammar, educationalAudience, Anglo-Saxon students]
-
A.
hasEducationalAudience
chosen
Indicates that something is intended for or directed toward a specific educational audience or learner group.
-
B.
educationalFocus
Indicates the primary subject area or theme that an educational activity, program, or resource is centered on.
-
C.
educationUse
Indicates the use or application of something specifically for educational purposes or in an educational context.
-
D.
educationalContext
Indicates the situational or institutional setting in which an educational activity, interaction, or resource takes place.
-
E.
typicalAudience
Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
- 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_69bd443fc49c819089629c00e311310c |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7563ad608190879a26a0bf07c3f6 |
completed | March 20, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69bd715c0a448190afc837c6c31dc6ab |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:40 p.m.