Triple
T21029814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosae Rubeae et Aureae Crucis |
E518033
|
entity |
| Predicate | teachingScope |
P48722
|
FINISHED |
| Object | advanced magical theory |
—
|
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: advanced magical theory | Statement: [Rosae Rubeae et Aureae Crucis, teachingScope, advanced magical theory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teachingScope Context triple: [Rosae Rubeae et Aureae Crucis, teachingScope, advanced magical theory]
-
A.
scopeOfTeaching
chosen
Indicates the range, subjects, or areas that a teaching activity, role, or responsibility covers.
-
B.
coreTeaching
Indicates that an entity serves as a primary or foundational teaching or instructional activity for another entity.
-
C.
definedTeaching
Indicates that one entity has formally specified or established the teaching content, method, or curriculum for another entity.
-
D.
targetsTeaching
Indicates that one entity is the intended focus or recipient of another entity’s teaching efforts or instructional activities.
-
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_69e0b503275c8190afd9a163f997c709 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc7fd3ec81908ac237047f9b0d7a |
completed | April 21, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:55 p.m.