Triple
T26992511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3-SAT |
E679892
|
entity |
| Predicate | typicalAlgorithmicApproach |
P77723
|
FINISHED |
| Object | backtracking search |
—
|
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: backtracking search | Statement: [3-SAT, typicalAlgorithmicApproach, backtracking search]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAlgorithmicApproach Context triple: [3-SAT, typicalAlgorithmicApproach, backtracking search]
-
A.
standardApproach
chosen
Indicates that an entity uses or follows a commonly accepted, conventional, or typical method for addressing a task or problem.
-
B.
typicalProblem
Indicates that a situation, issue, or obstacle is representative or characteristic of the usual problems encountered in a given context.
-
C.
relatedAlgorithm
Indicates that one algorithm has a meaningful connection or association with another algorithm, such as similarity, dependency, or complementary function.
-
D.
typicalComplexity
Indicates the usual or characteristic level of complexity associated with an entity, process, or situation.
-
E.
guardedApproachTo
Indicates a cautious, defensive, or wary manner of moving toward or engaging with 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69ff49f888348190b9c55afa73b99e6a |
completed | May 9, 2026, 2:51 p.m. |
| PD | Predicate disambiguation | batch_69ff49614ef88190ac70b034c55ad738 |
completed | May 9, 2026, 2:49 p.m. |
Created at: April 27, 2026, 6:52 a.m.