Triple
T5258204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston School of painters |
E118753
|
entity |
| Predicate | teachingTradition |
P24055
|
FINISHED |
| Object | atelier-based instruction |
—
|
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: atelier-based instruction | Statement: [Boston School of painters, teachingTradition, atelier-based instruction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teachingTradition Context triple: [Boston School of painters, teachingTradition, atelier-based instruction]
-
A.
followsEducationalTradition
Indicates that one entity adheres to, continues, or is guided by the established educational practices, principles, or lineage associated with another entity.
-
B.
coreTeaching
Indicates that an entity serves as a primary or foundational teaching or instructional activity for another entity.
-
C.
mainTradition
Indicates that one entity represents the primary or dominant tradition associated with another entity.
-
D.
practicedTradition
Indicates that an entity engages in or carries out a particular tradition as a customary or repeated practice.
-
E.
typeOfTeaching
chosen
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_69bd446978108190bb5f9c5c23d93f88 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7bcced6881909bdb7ac5471a37fe |
completed | March 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69bd77c55224819096c0bcfcfae79bd3 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:50 p.m.