Triple
T36625490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMT-COMP |
E904157
|
entity |
| Predicate | evaluatesAspect |
P93446
|
FINISHED |
| Object | solver performance |
—
|
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: solver performance | Statement: [SMT-COMP, evaluatesAspect, solver performance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evaluatesAspect Context triple: [SMT-COMP, evaluatesAspect, solver performance]
-
A.
evaluationAspect
Indicates the specific dimension or criterion of performance or quality that is being assessed within an evaluation.
-
B.
validatedAspectOf
Indicates that one entity has been checked or confirmed as a correct, acceptable, or compliant aspect or component of another entity.
-
C.
testsAspect
chosen
Indicates that one entity evaluates, examines, or assesses a particular aspect, feature, or dimension of another entity.
-
D.
refersToAspect
Indicates that one entity specifically references or points to a particular aspect, feature, or component of another entity.
-
E.
onAspect
Indicates that one entity is positioned on a particular side, surface, or facet of 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_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.