Triple
T36625689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boolector |
E904161
|
entity |
| Predicate | supportsSMTLIBLogic |
P202555
|
FINISHED |
| Object | QF_BV |
—
|
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: QF_BV | Statement: [Boolector, supportsSMTLIBLogic, QF_BV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSMTLIBLogic Context triple: [Boolector, supportsSMTLIBLogic, QF_BV]
-
A.
theorySupports
Indicates that one theory provides justification, evidence, or logical backing for another claim, theory, or proposition.
-
B.
supportsInferenceOf
Indicates that one entity provides a logical basis or justification for concluding or deriving another entity.
-
C.
satisfiabilityType
Indicates the classification of how or whether a given condition, formula, or constraint can be satisfied (e.g., satisfiable, unsatisfiable, or unknown).
-
D.
supportsEquations
Indicates that one entity provides the capability to handle, display, or work with mathematical equations for another entity or within a given context.
-
E.
supportsSyntaxElement
chosen
Indicates that one entity provides compatibility or handling capability for a particular syntax element in another entity.
- 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.