Triple
T30846930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schenkerian school |
E785661
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | analytical tradition |
C57724
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: analytical tradition Context triple: [Schenkerian school, instanceOf, analytical tradition]
-
A.
historiographical tradition
A historiographical tradition is a coherent, historically developed approach to interpreting and writing about the past, characterized by shared methods, assumptions, and narrative patterns among historians.
-
B.
historical scientific tradition
A historical scientific tradition is a long-standing, culturally embedded pattern of scientific thought, practice, methods, and institutions that evolves over time within a particular community or civilization.
-
C.
linguistic tradition
A linguistic tradition is the historically developed and culturally shared system of language practices, norms, and conventions that shape how a community speaks, writes, and interprets meaning over time.
-
D.
ancient commentary tradition
The ancient commentary tradition is the sustained practice of interpreting, explaining, and expanding upon authoritative texts—often religious, philosophical, or legal—through successive layers of written exegesis across generations.
-
E.
metaphysical tradition
A metaphysical tradition is a historically and culturally situated body of teachings, practices, and assumptions that systematically explores and explains the fundamental nature of reality, being, and existence beyond empirical observation.
- F. None of above. chosen
Provenance (1 batch)
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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:46 p.m.