Triple
T34472105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gabriel localization theory |
E884934
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | theory in category theory |
C15783
|
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: theory in category theory Context triple: [Gabriel localization theory, instanceOf, theory in category theory]
-
A.
result in category theory
A result in category theory is a proven statement—such as a theorem, lemma, or proposition—about objects, morphisms, and functors that reveals structural relationships or properties within or between categories.
-
B.
tool in category theory
chosen
A tool in category theory is a conceptual or formal construct—such as functors, natural transformations, limits, or adjunctions—used to analyze, relate, and systematically reason about mathematical structures and their morphisms within the categorical framework.
-
C.
theory in homological algebra
A theory in homological algebra is a systematic framework that studies algebraic structures via chain complexes, exact sequences, and derived functors to capture and analyze their underlying relationships and invariants.
-
D.
theory in field theory
A theory in field theory is a specific, mathematically formulated model that assigns fields and their dynamics to spacetime, defining how physical quantities evolve and interact according to a chosen set of principles and equations.
-
E.
type theory
Type theory is a formal framework that classifies expressions by their types to ensure logical consistency and safety in mathematical proofs and programming languages.
- F. None of above.
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_69f349c880408190ade571c471ab154a |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:01 a.m.