Triple
T36625427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMT |
E904155
|
entity |
| Predicate | algorithmicTechnique |
P25130
|
FINISHED |
| Object | DPLL(T) |
—
|
NE NERFINISHED |
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: DPLL(T) | Statement: [SMT, algorithmicTechnique, DPLL(T)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: algorithmicTechnique Context triple: [SMT, algorithmicTechnique, DPLL(T)]
-
A.
algorithmicProperty
Indicates that a subject possesses a specific characteristic, behavior, or quality defined in terms of an algorithm or computational procedure.
-
B.
algorithmType
Indicates the specific kind or category of algorithm associated with an entity or process.
-
C.
relatedAlgorithm
chosen
Indicates that one algorithm has a meaningful connection or association with another algorithm, such as similarity, dependency, or complementary function.
-
D.
featuresTechnique
Indicates that something incorporates or makes use of a particular technique as part of its content or execution.
-
E.
algorithmVariant
Indicates that one algorithm is a variant or modified version of another algorithm.
- 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.