Triple
T32267217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isabelle/ZF |
E824318
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Isabelle object logic |
C26890
|
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: Isabelle object logic Context triple: [Isabelle/ZF, instanceOf, Isabelle object logic]
-
A.
SMT-LIB family
The SMT-LIB family is a standardized collection of logical theories, syntactic constructs, and benchmark formats designed to specify and exchange Satisfiability Modulo Theories (SMT) problems across different solvers.
-
B.
object-oriented specification language
An object-oriented specification language is a formal language used to precisely describe the structure, behavior, and constraints of object-oriented systems without necessarily providing an executable implementation.
-
C.
treatise on logic
A treatise on logic is a systematic, often formal written work that analyzes the principles of valid reasoning, argument structure, and inference.
-
D.
OBDA system
An OBDA (Ontology-Based Data Access) system is a framework that uses an ontology to provide a unified, semantic view over heterogeneous data sources, enabling users to query data at a conceptual level without needing to know the underlying schemas or storage details.
-
E.
higher-order logic theorem prover
chosen
A higher-order logic theorem prover is a software system that automatically or interactively checks, derives, and manipulates logical statements and proofs in a logic where functions and predicates can take other functions and predicates as arguments.
- 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_69f3490e73588190915f282edd105772 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:42 a.m.